SoylentNews is people
SoylentNews
Controversy is nothing new when it comes to systemd. Many people find this new Linux init system to be inherently flawed in most ways, yet it is still gaining traction with major distros like Arch Linux, openSUSE, Fedora, and soon both Ubuntu and Debian GNU/Linux. The adoption of systemd for Debian 8 "Jessie" has been particularly fraught with strife and animosity.
Some have described the systemd adoption process as having been a "coup", while others are vowing to stick with Debian 7 as long as possible before moving to another distro. Others are so upset by what they see as a complete betrayal of the Debian and open source communities that there is serious discussion about forking Debian. Regardless of one's stance toward systemd, it cannot be argued that it has become one of the most divisive and disruptive changes in the long history of the Debian project, threatening to destroy both the project and the community that has built up around it.
(Score: 3, Interesting) by Marand on Sunday September 28 2014, @02:57PM
For now, at least, it's still just a case of a software recommendation that eventually leads back to systemd. The problem there is that Recommends are usually installed automatically, so the average user is likely to conflate this with a requirement when it's still optional*.
As for Poettering's comment about not supporting systemd, that may be the case but there's still eudev (as you mentioned), and Debian has systemd-shim as a way to use other systemd (and udev) bits without requiring the init side. I don't know how long that will remain the case, but Debian has that kFreeBSD port, which can't use systemd, to consider, so it's hopefully going to last a while. Poettering and co. don't have any interest in non-Linux systems and kernels, and the longer it takes to port systemd elsewhere, the longer Debian will avoid complete tie-in.
If you don't have access to Debian or Ubuntu directly, you can look at Debian and Ubuntu deps at packages.debian.org and packages.ubuntu.com, respectively, for an idea of how their dependencies work out. If you do, though, apt-rdepends is probably the best way to check the dependency tree. Even allows output in a format springgraph (from signing-party package) understands for creating an image from the relationships.
---
* For the curious: synaptic has a checkbox to turn this off; apt-get has --no-install-recommends switch; aptitude has a checkbox to disable it; or you can change it by hand by putting APT::Get::Install-Recommends "false"; in a file in /etc/apt/apt.conf.d/
I turned off auto-recommends years ago because it kept trying to add a lot of insane cruft I didn't care about. Good default for newbies, crap setting for Linux vets.
(Score: 2) by tonyPick on Sunday September 28 2014, @03:51PM
I don't know how long that will remain the case, but Debian has that kFreeBSD port, which can't use systemd, to consider, so it's hopefully going to last a while.
Yes, but it's pretty clear that the solution to that is that "supporting the kFreeBSD port isn't important" by at least some of the package maintainers, so I'm less hopeful.
Skip to around 21:30 in this (Michael Stapelberg from Debconf 2013): http://www.youtube.com/watch?v=Hvy0e9kbAos [youtube.com] and the first two questions cover this (or watch it all; it's rather good and not very long).
(Score: 1) by canopic jug on Monday September 29 2014, @09:43AM
It's on the chopping block [debian.org] as far as jessie is concerned due to needing more porters. If a few more porters show up very, very soon, then the risk goes down.
Money is not free speech. Elections should not be auctions.
(Score: 2) by Marand on Monday September 29 2014, @10:27AM
Great, if that happens, we'll be lucky if the systemd-shim lasts beyond jessie's release. :( One Redhat to rule them all...