Bas Wijnen <wij...@debian.org> writes: > On Fri, May 09, 2014 at 10:37:03PM +0200, Tollef Fog Heen wrote:
>> It and upstart (and any other providers of /sbin/init) should also grow >> critical debconf warnings if you install them and you were previously >> using systemd as your init so it's symmetric. > Nobody is suggesting that systemd should give you a critical warning > when you try to install it. The problem people are having, is that it > suddenly installs itself without the user trying. When sysv init or > upstart do that, they should get critical warnings as well. But better > yet, they shouldn't do it. And neither should systemd. The same issue that leads to systemd being installed could well lead to one of the other init systems being installed for the same reason: some piece of software integrates with only one init system and Depends on it. If we can avoid that situation, great -- portable software is always good. But belt and suspenders: we should also prepare for that situation and ensure that any switch of an init system via package installation results in a critical debconf warning so that no one is caught by surprise. This has the advantage of future-proofing against any later change of init system, letting us reuse the mechanisms that we put in place for this one. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87zjiqsh1e....@windlord.stanford.edu
