SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Some things (OBS, calibre, handbrake) are already building against it, too.
But qt5 etc can be adopted on slackbuilds as ever when new version replace older , like qt4 or qt3 , and packages you mentioned are not in stock slackware distribution , are 3rthd party packages.
In some case , nothing strange if stuck on qt5 , and next release stucks on qt5 + plasma5 , i remember perfectly when 14.2 released under qt4/kde4 when qt5/plasma5 are available but no switched.
In all cases , too work remaining , like upgrade python3 , remove python2 , upgrade ssl to version 3 etc etc.
Last edited by USUARIONUEVO; 01-25-2023 at 10:19 PM.
A couple possible additions I think might be useful for the next release:
1. radvd - ipv6 router advertisement daemon
2. postgresql (including building support for it into anything qt and kde related, to allow for the use of pgsql for services such as akonadi if supported)
Right now they released their 2.5.1. version and they can be built with autotools.
Grounds: it is the standard Unix desktop environment. I would make sense to have it in Slackware, which is the most Unix-like of all linuces.
The Unix philosophy is one thing, but it should not override the Slackware philosophy
Additions in Slackware are very rare
Changelogs speak for themselves
ps: I deliberately did not count the other series (a/ d/ l/ ...), since they are more or less always necessary additions.
And ap/ xap/ seem to me to be more reflective of extra user requests
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.