Requests for current-next (15.0-->15.1)

ReaperX7 · 03-01-2022, 02:19 PM

Quote:

Originally Posted by business_kid

Agreed. I'm just suggesting that Mate sucks less, and is otherwise XFCE. If not replace, perhaps add the mate desktop which is only 1 or 2 packages which are already made. While I'm making suggestions that won't be acted on, let me add 2

A Word processor
VLC - which has topped LQ's annual lists forever.

Candidates for ejection might be

Compilers/debuggers for less used languages (e.g. fortran, ada) - in the popularity stakes, they lose.
Seamonkey - popularity.
All 1990s pci bus video card drivers which more proper belong in antique collections.
All little used exotic TTF fonts which should be farmed out to somebody's repo.
All fixed width fonts along with anything using them (e.g. xine).
All support for obsolete or nearly obsolete internet protocols (irc, jabber, etc).
All "Look clever in ascii" utilities. Wasting dvd space.

A lot of packages are used as dependencies by other packages, or they still serve a purpose because "they just work". Your suggestions are based entirely on opinion from a singular point of view. Your own view, not others. What you find useless, others will find useful.

A lot of what you describe are still packages that are quite standard still. If Patrick is still including stuff for a reason, then it's his reasoning.

If you want a more custom system, there's always ArchLinux, Gentoo, LFS, or even FreeBSD.

Slackware is what it is. You get what you get, and you don't throw a fit.

Pixxt · 03-01-2022, 04:30 PM

MPlayer 1.5

https://mplayerhq.hu/design7/news.html

https://mplayerhq.hu/MPlayer/releases/ChangeLog-1.5

bassmadrigal · 03-01-2022, 04:35 PM

Quote:

Originally Posted by Pixxt

MPlayer 1.5

https://mplayerhq.hu/design7/news.html

https://mplayerhq.hu/MPlayer/releases/ChangeLog-1.5

Plus ffmpeg 5.0, which has really sad release notes (but the Changelog is a little better).

MPlayer 1.5 provides full support for ffmpeg 5.0.

marav · 03-01-2022, 07:55 PM

Seamonkey 2.53.11

Release notes:
https://www.seamonkey-project.org/re...monkey2.53.11/

avian · 03-01-2022, 11:59 PM

Smartmontools 7.3

Quote:

Smartmontools 7.3 brings smartctl support for getting/setting SMART persistent power-on values (and being able to restore them to manufacturer defaults), support for checking the NVMe 1.4 status bit with the -H argument, support for zoned block device characteristics and statistics, improved JSON output handling for the smartctl utility, a variety of Linux / OpenBSD / FreeBSD / Windows specific fixes, and various other fixes and enhancements.

https://www.smartmontools.org/

marav · 03-02-2022, 04:39 AM

Digikam 7.6.0

https://invent.kde.org/graphics/digikam/-/tags/v7.6.0

gmgf · 03-02-2022, 06:23 AM

poppler-22.03.0:

https://poppler.freedesktop.org/

https://poppler.freedesktop.org/poppler-22.03.0.tar.xz

John Lumby · 03-02-2022, 08:02 AM

Quote:

Originally Posted by business_kid

[...]

Candidates for ejection might be[LIST]

[...]
[*]All fixed width fonts along with anything using them (e.g. xine).

I am surprised that one did not raise a howl of protest, but I will do my best :
NOOOOOOO
That would leave every emacs user needing to go find it in extra or pasture and then staring at ruined indentation and tabulation.

Cheers, John Lumby

business_kid · 03-02-2022, 09:13 AM

Quote:

Originally Posted by John Lumby

I am surprised that one did not raise a howl of protest, but I will do my best :
NOOOOOOO
That would leave every emacs user needing to go find it in extra or pasture and then staring at ruined indentation and tabulation.

Cheers, John Lumby

OK - folks have shot down everything else I suggested. I didn't know emacs was on fixed width fonts. Mind you, I am bemused by most vi & emacs enthusiasts. I know folks do clever things with keyboard shortcuts. It kinda reminds me of folks doing programming in machine code, at least one of which I knew.

EDIT: Somebody said Calligra was a word processor. I ran up a liveslak and gave it a spin. I agree it fits the definition of 'word processor' and probably beats M$ Wordpad but it's definitely in the relegation zone.

kjhambrick · 03-02-2022, 11:32 AM

Quote:

Originally Posted by John Lumby

... NOOOOOOO ...

John Lumby

+1

How does one write readable code with a proportional font ?

-- kjh

bassmadrigal · 03-02-2022, 02:44 PM

Quote:

Originally Posted by kjhambrick

How does one write readable code with a proportional font ?

Plus, maybe it's just me, but I'd hate to use a terminal with a proportional font. And I'm in the terminal a lot.

business_kid · 03-02-2022, 03:36 PM

Quote:

Originally Posted by kjhambrick

How does one write readable code with a proportional font ?

Do you mean screen readable or print readable? If it's not to your taste, adjust the font size. Fixed width fonts were fine when everyone was on 80x25 monitors and printing on 132 character dot matrix printers with typewriter ribbons. 640x480 was vga! But things have moved on. I'm on 1600x900 & hdmi and others on 4k screens.

Some of the thinking on this thread should be about future-proofing slackware, surely?

Didier Spaier · 03-02-2022, 03:59 PM

@business_kid: kjhambrick meant that when reading computer code you need to know the indentation of the code to understand what it does. This is impossible with a variable font width.

kjhambrick · 03-02-2022, 05:01 PM

Thanks Didier Spaier

Yes, Python Scripts for example, would be subject to frequent and almost incorrectable breakage due to its dependence on indentation depth for code block interpretation (

icky but that's another issue

).

And I would lose even more of my meager mind when I have to create and maintain inline tables of values.

-- kjh

GazL · 03-02-2022, 05:32 PM

Quote:

Originally Posted by Didier Spaier

@business_kid: kjhambrick meant that when reading computer code you need to know the indentation of the code to understand what it does. This is impossible with a variable font width.

Beginning of line indentation would still work even with variable width fonts, but you lose the ability to beautify something like this:

Code:

static const char *colors[SchemeLast][2] = {
                       /*  --fg--     --bg-- */
        [SchemeNorm] = { "#bbbbbb", "#222222" },
        [SchemeSel]  = { "#eeeeee", "#005577" },
        [SchemeOut]  = { "#000000", "#00ffff" },
};

Formatting struct initialisation data into tables is quite a common way of improving readability.

No thanks, I'll stick to fixed width character cells for code.