Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 14 submissions in the queue.

KDE Will Depend on 'logind' and 'timedated' in 6 Months

posted by janrinok on Friday February 20 2015, @01:18PM   Printer-friendly
from the and-perhaps-it-will-work dept.

jbernardo writes:

Earlier this week, KDE developer David Edmundson described in his blog how KDE would be tied to logind and timedated but not systemd itself, at least according to his claim that "The init system is one part of systemd that doesn't affect us at all, and any other could be used.".

Later, in the blog comments, he clarifies that starting with plasma 5.5, in 6 months, they'll drop "legacy" support, according to a decision taken in the plasma sprint.

Even if one can only guess why there is no formal announcement, it seems clear - unless somehow there is a shim or emulator, not only for logind but also for timedated, in 6 months KDE will be unusable unless you are running systemd. And the blog entry makes it clear that the plan is to remove more and more functionality from KDE and use systemd instead.

 
This discussion has been archived. No new comments can be posted.
KDE Will Depend on 'logind' and 'timedated' in 6 Months | Log In/Create an Account | Top | 131 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by Arik on Friday February 20 2015, @06:38PM

    by Arik (4543) on Friday February 20 2015, @06:38PM (#147504) Journal
    "4. KDE's "terrible launch" was the result of them deciding to call the pre-release 4.0, and a bunch of distros ignoring warnings not to package it yet. Debian didn't switch to KDE4 until 4.3 or so and it was smooth transition to a pretty stable desktop by then. Blame your distro for making a bad decision, not KDE for creating a pre-release."

    No, I'll blame the distros for their decisions, and still have plenty left over for the KDE team calling an alpha '4.0' as well as for abandoning a system that was nearing maturity and starting over for no compelling reason and with no thought whatsoever for the users they screwed over in the process.

    "Bitching about systemd is great and all, but don't pretend init was standard prior to systemd init being shoved down our throats by Poettering and pals. It just seemed like it if you never switched distros or looked too closely at the parts under the hood."

    Sounds like you completely missed the point on systemd. Yes, we had (and have) many different init systems - THAT IS GOOD. They all play nicely except for systemd, and THAT is the biggest problem with systemd - not that it is Yet Another Init System but that it is the one that is by design hostile to all the things that make *nix systems worth using, and refuses to play nicely with the ecosystem. It's  a cancer.

    Linux would be fine if someone would just be a dear and kill Redhat.

    --
    If laughter is the best medicine, who are the best doctors?
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 0) by Anonymous Coward on Sunday February 22 2015, @09:48AM

    by Anonymous Coward on Sunday February 22 2015, @09:48AM (#148048)

    Yep. At this point in time talking about systemd as a "mere" init is a distraction. It has pretty much reimplemented anything not coreutils.