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.
Pat, perhaps it's time to put qt5 on current (just suggestion)
Why not LinuxPAM, instead?
It is much much much more simple to add four packages and to recompile a few, than putting down the very stable KDE4, as you "innocent" suggest...
And to replace KDE4 with what? With The Ugly Thing which only its mommy love it?
Oh, also to note that The Ugly Thing got the SystemD way. We add also SystemD to the check list, for a proper work of The Ugly Thing?
I'm not against, but not for, either...
Still, bear in mind that if Slackware does not want to jump on bed with SystemD in one bright day, KDE4 is the last KDE which you should want to see on Slackware.
Last edited by Darth Vader; 01-30-2017 at 05:01 PM.
It is much much much more simple to add four packages and to recompile a few, than putting down the very stable KDE4, as you "innocent" suggest...
And to replace KDE4 with what? With The Ugly Thing which only its mommy love it?
Oh, also to note that The Ugly Thing got the SystemD way. We add also SystemD to the check list, for a proper work of The Ugly Thing?
I'm not against, but not for, either...
Still, bear in mind that if Slackware does not want to jump on bed with SystemD in one bright day, KDE4 is the last KDE which you should want to see on Slackware.
Perhaps it's time to replace that tape of yours Darth Vader. The tune is getting quite boring.
I wouldn't mind if applications written for qt4 would still compile.
I don't mean kde4 only.
--
Best regards,
Andrzej Telszewski
Do you mean software included with Slackware, or third-party? Eventually, the move to Qt5 is going to have to happen. I imagine Qt4 will move to SBo when Qt5 makes its way into the next -stable release. Similarly with Python, though I'm not sure if that will happen in the next release.
It is much much much more simple to add four packages and to recompile a few, than putting down the very stable KDE4, as you "innocent" suggest...
And to replace KDE4 with what? With The Ugly Thing which only its mommy love it?
Oh, also to note that The Ugly Thing got the SystemD way. We add also SystemD to the check list, for a proper work of The Ugly Thing?
I'm not against, but not for, either...
Still, bear in mind that if Slackware does not want to jump on bed with SystemD in one bright day, KDE4 is the last KDE which you should want to see on Slackware.
It's true that you know in ugly thing Darth Vader, you should change chorus, from time to time.
Oh, also to note that The Ugly Thing got the SystemD way. We add also SystemD to the check list, for a proper work of The Ugly Thing?
Well that is not true. Without Wayland, there is no need for anything systemd related. The Wayland compositor wants to use the logind d-bus API. That is not the same as "wants to use systemd". KWin in Plasma 5 does not care if it is systemd-logind, or elogind, or any other future implementation which provides the d-bus service.
Do you mean software included with Slackware, or third-party? Eventually, the move to Qt5 is going to have to happen. I imagine Qt4 will move to SBo when Qt5 makes its way into the next -stable release. Similarly with Python, though I'm not sure if that will happen in the next release.
You're correct, I forgot about SBo. So, actually nothing against qt5.
I wouldn't mind if applications written for qt4 would still compile.
I don't mean kde4 only.
FWIW, here is the list of packages included in Slackware 14.2 that rely on qt4 and do not belong to the kde series of packages (could be slightly inaccurate, but you get the idea):
I believe that some of the packages you listed are really here because of KDE4, i.e. akonadi.
And others would probably compile against qt5. Probably not all, though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
