| > They made systemd the default, but maintained the ability to switch to another init system [1] No, they didn't. You can't install debian without systemd. They _said_ they let you switch, but they don't. People did not fork an entire distro just because they didn't like to press "option B" instead of "option A". > If this is "essentially forcing" the use of systemd, then what possible choice would have counted as not forcing it other than making sysv the default? 1. Not having packages depend on systemd. 2. Bringing up a prompt/dialog during installation to make a choice of whether or not to use it. > most of the developers are still working on the original project Because Devuan is just Debian with some tiny changes and a different choice of packages. And of course, the infrastructure of a project - website, forum, IRC, download servers, etc. So of course most developers aren't concerned with that, they just provide/maintain upstream packages. > Obviously, this is almost as contentious as systemd was I didn't know about this aspect, thank you. |
This implies either (a) refusing packages that depend on systemd, or (b) patching packages. Which brings us right back to the original problem: who's on the hook for making sure it works?
> 2. Bringing up a prompt/dialog during installation to make a choice of whether or not to use it.
https://www.joelonsoftware.com/2000/04/12/choices/
... okay, I admit I also need to offer a reason why it's okay for Debian to offer the install options that they do offer, while they also refuse to offer this option, and can't really come up with one. The way that Debian allows you to pick a desktop environment at install time, while not allowing you to pick an init system, is a bit of an arbitrary decision.
But the decision being arbitrary isn't a reason to offer every single theoretically possible option at install time. Debian never allowed you to pick an init system at install time before! Why start now?