Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required
On Tue, Jul 23, 2019 at 11:15 AM Sean Whitton <spwhitton@spwhitton.name> wrote:
>
> I think that the wording for this change should reflect the above
> (unless I've misunderstood David), such that the new wording cannot be
> misinterpreted to mean that the sysvinit requirement does not apply to
> any package using any systemd component.
That would resolve my issue, though I am not sold on the value of the
additional specificity. I'll say no more than this - If I am operating in good
faith, the additional language is not necessary. If I am not, it won't stop
me.
Dave
Reply to: