Debian Developers Take To Voting Over Init System Diversity
It's been five years already since the vote to transition to systemd in Debian over Upstart while now there is the new vote that has just commenced for judging the interest in "init system diversity" and just how much Debian developers care (or not) in supporting alternatives to systemd.
Due to Debian developers having differing opinions on handling non-systemd bugs in 2019 and the interest/commitment to supporting systemd alternatives in the scope of Debian packaging and various related friction points, they've taken to a new general resolution over weighing init system diversity.
The ballot is available on-line. The choices are:
Choice 1: F: Focus on systemd
Choice 2: B: Systemd but we support exploring alternatives
Choice 3: A: Support for multiple init systems is Important
Choice 4: D: Support non-systemd systems, without blocking progress
Choice 5: H: Support portability, without blocking progress
Choice 6: E: Support for multiple init systems is Required
Choice 7: G: Support portability and multiple implementations
Choice 8: Further Discussion
[Ed. note: I'm not sure what the letters after the choice numbers indicate, nor do I know where "C" disappeared to.]
(Score: 3, Insightful) by Arik on Tuesday December 10 2019, @07:58PM (2 children)
And Android is an excellent example of what should never be done. On just about every level. So I'm not even sure if you replied to the right message.
It's a bit mystifying.
If laughter is the best medicine, who are the best doctors?
(Score: 2) by epitaxial on Tuesday December 10 2019, @09:10PM (1 child)
It perfectly describes your problem of packaging. There are competing formats that all do the same thing and now that systemd is involved it makes things much worse.
(Score: 1) by Arik on Wednesday December 11 2019, @05:08AM
Not my problem. Again, I suspect you are replying to the wrong messages for some reason.
If laughter is the best medicine, who are the best doctors?