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

[Dmitry Bogatov <KAction@disroot.org>]

[2019-09-26 17:48] Ansgar <ansgar@43-1.org>
> On Thu, 2019-09-26 at 15:26 +0000, Dmitry Bogatov wrote:
> > If this is the case, I'd propose wording like following:
> > 
> >   [ ... All packages with daemons must provide init.d scripts ...],
> >   unless software is only usable, by upstream's design, when pid1 is
> >   provided by some alternative init system. In such case, it must Depend
> >   on that alternative system (e.g binary package, that provides
> >   corresponding version of /sbin/init).
>
> Such a dependency shouldn't be added as one can run software in
> containers or so and talk to the outside systemd instance.  Note that
> iptables doesn't depend on the linux kernel package either.

Reasonable. Then let's drop part about Depends:

	[ ... All packages with daemons must provide init.d scripts ...],
	unless software is only usable, by upstream's design, when
	pid1 is provided by some other init system.

> Also sysvinit would be an "alternative init system" given the current
> default.

As you wish. s/alternative/other/.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.