Bug#932704: Fwd: Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required
Re-sending to the bug thread.
---------- Forwarded message ---------
From: David Steele <steele@debian.org>
Date: Mon, Jul 22, 2019 at 9:15 AM
Subject: Re: Bug#932704: debian-policy: Don't force sysvinit
compatibility if e.g. alternate init required
To: Sean Whitton <spwhitton@spwhitton.name>
On Mon, Jul 22, 2019 at 7:02 AM Sean Whitton <spwhitton@spwhitton.name> wrote:
>
> We would want to be careful to word this requirement such that it did
> not license maintainers to do things which block the work of those who
> don't like systemd.
>
> --
> Sean Whitton
The use of the systemd API blocks the work of those who don't like
systemd. Is that something that should that be addressed by Policy? I
don't think so.
Under the scenario where the systemd api is used by a package, the
current Policy leads down a logical path resulting in vestigial init
scripts with calls to systemctl. Is that a preferred result, relative
to the proposed exception?
I don't see how that ultimately meets anyone's goals for alternate init support.
--
AE0D BF5A 92A5 ADE4 9481 BA6F 8A31 71EF 3661 50CE
Reply to: