Bug#727708: On diversity
Anthony Towns <aj@erisian.com.au> writes:
> To me that seems like it would be a bad outcome (even if we adopted
> upstart everywhere and abandoned sysvrc, systemd and openrc entirely; it
> would still make it unduly difficult to experiment with the next
> next-generation init systems in a Debian environment). I'd expect the
> tech ctte's decision to be prescriptive enough that it's clear what
> non-default-init-system maintainers and users should do,
> post-apocalypse, I guess.
For as long as they're interested in making the effort, try to get as many
packages as possible supported under their init system, particularly in
advance of the point at which we might start dropping sysvinit scripts
that currently provide the common denominator across all the systems.
Obviously, to the extent that this can reuse work done for the default
init system, that's going to make this much easier. That means that
implementing the key integration features of the default init system will
make things much easier (for example, things like the notification
protocol, non-forking daemon startup, and possibly socket activation).
It's going to be particularly important to have good docs for maintainers
to write configuration for the non-default init system, since a lot of
maintainers aren't going to be able to easily test, so you want people to
be able to write things that work without a lot of debugging. Obviously,
that includes Policy.
> On a practical note, having a quick look at the policy list, it seems
> like that's not actually crazy active/responsive at present either (long
> overdue updates to menu policy and triggers documentation are the only
> topics this month?), so relying on -policy for detail work doesn't seem
> like it would actually work out in a timely fashion?
Policy is in general not horribly healthy right now, but as I mentioned in
passing earlier in this huge thread, I'm committing to shephard the Policy
work for this decision through and try to help with the documentation and
specifics. I can't do that and participate in this discussion at the same
time, though, since this is basically eating all my Debian time at the
moment.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: