What is the Plan for integration of Plasma 5 into Current?
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.
Y'all wrong. What [I] am waiting for is the only thing that [I] really want and that [I think] really matters nowadays in Linux : systemd integration
---------->
You ought to be redfaced; what I have a mind to tell you is to wash your mouth out with soap! The mere suggestion of systemd anythihg is vomit-inducing, to put it mildly.
Geez! What am I missing? Why are people still acting as if Plasma5 is the major obstacle to Slackware 15 release? [...] So why is Plasma5 perceived as THE Holdup?
So what else? must be big and monolithic so we don't see sign of it in the Changelog (or do we?)
What could be THE Holdup if not KDE5?
- replacing gcc with llvm (and dropping gcc)?
- replacing glibc with musl libc?
- dropping gtk (and xfce) and focusing on a qt5 / KDE5 only distro?
- waiting for Christmas because giving presents before is bad form?
I know the radio silence is part of the Slackware culture. At this stage, after more than four years without a stable release, I think the silence is increasingly eroding the user base.
You ought to be redfaced; what I have a mind to tell you is to wash your mouth out with soap!
Heh. Don't take the bait.
KDE-plasma will be a very welcome addition to Slackware. Yes. This has been a long release cycle. Windows 10 has been around longer than 4 years. CentOS 8 took a long time to arrive. Slackware 15.0 will arrive. Patience.
Geez! What am I missing? Why are people still acting as if Plasma5 is the major obstacle to Slackware 15 release? Again, PAM and elogind introduced a wrench to the gearworks but that was quickly resolved and wasn't specifically a Plasma5 problem AFAIK. And yet again, KDE v4 was absolutely HORRIBLE when it first came to Stable despite Patrick wisely waiting to include it. KTown/Plasma5 has never been horrible other than what I see as possibly valid complaints about mainly appearance. Even given that Plasma5 kicks sand in the face of original Slackware KDE4 (granted it later got really good). Do you guys not recall how badly original KDE4 ran in Stable? So why is Plasma5 perceived as THE Holdup?
PAM is in yes, but as far as I see elogind is not in --Current still, consolekit2 is. So I assume that is the monkey wrench that is still stuck in the gears?
PAM is in yes, but as far as I see elogind is not in --Current still, consolekit2 is. So I assume that is the monkey wrench that is still stuck in the gears?
To replace ConsoleKit2 with elogind is just need to:
- remove ConsoleKit2
- install elogind
- patch DBUS for elogind support
- patch polkit for elogind support
That's all.
I tell you as someone who did this elogind transformation even on boxes with stock KDE4 and XFCE, to use the skype4linux. And guess what? Even the stock KDE4 works fine with elogind - probably believing that it has a systemd-logind server.
Compared with ConsoleKit2 which requires to modify the software to understand its API, elogind implements the login1 API from systemd, as expected by the today software, which works with no modifications.
The fears of elogind are way unfounded and replacing ConsoleKit2 is way more simple than you think.
Last edited by LuckyCyborg; 10-19-2020 at 01:57 AM.
I know the radio silence is part of the Slackware culture. At this stage, after more than four years without a stable release, I think the silence is increasingly eroding the user base.
Did you do not seen that slackware-current was basically switched to maintenance mode and its development is almost nonexistent?
Permit me to doubt that they have any plans to release Slackware 15 in the years to come.
That's probably one of the true reasons why they just do no bother with Plasma5, as they know that Plasma5 will be EOL since long time and Plasma6 will be a fine and stable thing before any real release plans.
Last edited by LuckyCyborg; 10-19-2020 at 12:50 AM.
You ought to be redfaced; what I have a mind to tell you is to wash your mouth out with soap! The mere suggestion of systemd anythihg is vomit-inducing, to put it mildly.
You took my post much too seriously ! Was a joke, I'm glad Slackware is free of that crap
I'm more worried about slackware introducing systemd than anything else. It probably won't happen, but if it does happen, a devuan like split from slackware would become a serious possibility.
I'm more worried about slackware introducing systemd than anything else. It probably won't happen, but if it does happen, a devuan like split from slackware would become a serious possibility.
Most Slackers are exactly that: slackers. Why do you think no one picks up on all these calls for participation on the forum for spin-offs and side-projects...
Not that I think systemd will be added. We already use udev, and may end up using logind, but these are acceptable pieces of technology implementation that were extracted from systemd sources and now separately maintained.
Slackware indeed has dependencies resolution, the dependencies/dependent lists are just not public. Else, to give just one example, how Pat would know which packages need a rebuild when he upgrades icu4c?
Dependency information is built in to the ELF files. Anyone can construct the dependency matrix (it has ~10M cells and is 98% sparse).
Ed
And not all dependencies are built into the ELF for binary files. Sometimes they're just runtime dependencies.
And ruby... Further, some dependencies can be needed for optional features, and the versions are not always easy to track. I use depfinder for George Vlahavas but always review the output and complete/edit it whenever needed. Not to forget that there exist dependencies on various scripts, and on an a shell. It happened to me that some software I wanted to ship depended on a bash feature only available in newer version than the one I use.
Last edited by Didier Spaier; 10-19-2020 at 11:26 AM.
Reason: s/Me, //
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
