Bug#944801: debian-policy: must all inits support /etc/insserv/override & /usr/share/insserv/override

[Ansgar <ansgar@43-1.org>]

Control: retitle -1 debian-policy: [9.11] remove requirement that alternative inits must support sysvinit scripts

>> 9.11 states:
>> 
>> +---
>> > Alternative init implementations must support running SysV init
>> > scripts as described at System run levels and init.d scripts for
>> > compatibility.
>> +---

Thinking a bit more about this, I think this requirement should just be
removed from Policy.  It should be left to the individual communities
interested in a particular init system how much compatibility with
sysvinit is useful for them.

As an example, it might also be possible to just ignore sysvinit scripts
and use just init-specific jobs.  Or only use information from systemd
.service files.  Or only start services from a daemontools-style service
tree.

This might provide less coverage for packages in the archive, but if the
people using the init are fine with that then I don't see why Policy
should forbid it.

That would pretty much "solve" all questions I raised (except for
switching between init systems, but that's a different problem).

(Note that this is just about the requirement that alternative init
systems must be able to run/understand sysvinit scripts; it's not about
whether packages must/should provided sysvinit scripts which is more
controversial.)

Ansgar