6 ms·
If all these people dropping out of Debian is due to systemd, somebody needs to step up and force some kind of compromise. (I have no clue who; does Debian have
by peterwwillis 12y ago
If all these people dropping out of Debian is due to systemd, somebody needs to step up and force some kind of compromise. (I have no clue who; does Debian have a Dictator For Life position?) I may not like systemd, but I sure as shit would find some way to coexist with it rather than drive people away from a project.
- lmm 12y ago> If all these people dropping out of Debian is due to systemd, somebody needs to step up and force some kind of compromise. That's what Ian Jackson proposed - that while systemd would be the default, Debian would fully support users using other systems (bugs that only affected SysV users would be considered equally critical). He was voted down, hence his resignation. The systemd folks don't seem to be interested in compromise.
- Xylakant 12y agoFrom what I gathered following the discussion the problematic option was actually "no package that depends on systemd and does not provide an alternative that works with sysV is permitted". That would require that somebody provides the code to make the alternative way viable, work that neither the upstream would do nor the maintainers were willing to shoulder. It's fine to make that demand, but if you do, IMHO you should also step forward and say "and because this is what we propose, we will be providing said code."
- teddyh 12y agoYes. Saying “We permit systemd to exist in Debian, but we will not permit any packages which uses systemd’s extra features or advantages.” is hardly a compromise.
- wtbob 12y agoNeither, of course, is saying, 'we will permit packages to fail to work with any init system other than systemd.'
- Xylakant 12y agowhy not? If a package leverages functionality that only systemd provides and users want to have install package, they have to bite that bullet and install systemd. What are the alternatives? You can't force the upstream or the package maintainer to invest the extra work to make the package work without systemd, you're not providing the required work either and you certainly don't want the user to be on the loosing side because you don't like systemd.
- lmm 12y ago> you certainly don't want the user to be on the loosing[sic] side because you don't like systemd. Debian has a long and glorious tradition of standing on principle to the user's (at least short-term) detriment. Look at the way they used to ship KDE programs (especially in the days before GPLed Qt), or the way they still package tomcat, or their approach to multimedia codecs.
- teddyh 12y agoWhy not? This thing here, where a package fails to work without another specific package, is called a dependency, and that is is the normal way to do things. Just because you don’t like package A does not allow you to “compromise” by allowing A but not allowing B, C or D to have a dependency on A.
- mkesper 12y agoThis would have tied Debian to SysV forever, sucking up manpower needed for more fruitful work.
- coldpie 12y agoI can't imagine how much effort that would take to maintain. Arch Linux tried it and dropped the idea after a few short months.
- stinos 12y agoAnyone knows how this could be done in practice? I mean, in programming you'd solve a problem like this by defining a proper set of interfaces and making sure each implementation adheres to it. Form what I read in this thread, part of the problem seems to be there is no such interface and hence developpers depeninding on an init system have to choose A or B or do twice the work.
- peterwwillis 12y agoFrom what I understand of systemd, it's more a factor of there being an entirely new inter-process communication mechanism, combined with a lot of custom applications. And because it's this top-down monolithic design, either you use systemd as your init, or you get none of the functionality of the custom programs... so it's all-or-nothing. On top of that, the people who don't want to use it are against the idea of supplanting the core technology they're used to. So you have this one camp that's all "fuck yeah new technology", and another camp that's like "get that shit out of my box." In a way it's like GNOME vs KDE, but almost at the very heart of the operating system. You just have to pick one and go with it, or you don't really get the benefit of either. The 'set of interfaces' you mention should (imho) be patches to systemd to allow it to work as not-pid-1, so that you can still take advantage of its contributory applications without having to supplant your init system. That way you could use 'a gtk application in a kde workstation', but with systemd and sysvinit.