Bug#727708: Init system resolution open questions
On 19/01/14 12:20, Adrian Bunk wrote:
> Why do you want Debian to support multiple init systems in the first place?
I think because:
* whichever is chosen as default, there will be some users who
specifically don't like it, or specifically want something else
(including major consumers like Ubuntu (Upstart), or Spotify (systemd),
or Google (SysV))
* the non-Linux ports may have no choice but to get some other init
system working anyway (if systemd is chosen as the default on Linux - I
am quite certain it would never be ported)
* if people are going to be doing the above work anyway, let's make it
available to everyone, Linux and non-Linux users alike
* if the chosen init system turns out to be a disaster, we'd have an
easy way out if we weren't fully reliant on it; or maybe another init
system comes along for jessie+1, better than anything we have now, we'd
have more agility in being able to adopt it right away (not like this
current situation)
> What level of support (if any) would that guarantee for Debian's ports
> to non-Linux kernels?
I don't think anyone can guarantee that in a volunteer project; nobody
can be forced to do the work if they don't want to. Porters may have to
work hard and restore any lost functionality they care enough about. I
imagine such problems will be RC-severity bugs, so it should be possible
within existing practices to get patches applied or NMUd.
Regards,
--
Steven Chamberlain
steven@pyro.eu.org
Reply to: