Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required

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

Dmitry Bogatov writes:
> --- a/policy/ch-opersys.rst
> +++ b/policy/ch-opersys.rst
> @@ -1006,7 +1006,9 @@ supported by all init implementations. An exception to this rule is
>  scripts or jobs provided by the init implementation itself; such jobs
>  may be required for an implementation-specific equivalent of the
>  ``/etc/rcS.d/`` scripts and may not have a one-to-one correspondence
> -with the init scripts.
> +with the init scripts. Another exception is when software is only
> +usable, by upstream's design, when pid1 is provided by some other init
> +system.

I don't believe this is a good solution as the list of exceptions would
be cumbersome to maintain (cf. #911165).

Ansgar