Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required
[2019-09-25 11:50] David Steele <steele@debian.org>
> On Wed, Sep 25, 2019 at 11:43 AM Dmitry Bogatov <KAction@disroot.org> wrote:
> >
> >
> > [2019-09-22 16:13] David Steele <steele@debian.org>
> > > Candidate language attached. It adds "Also excepted are packages which require a
> > > feature of an alternate init system which is not available in SysV-Style
> > > init systems.". Thoughts?
> >
> > Imho, it opens loophole.
> > [...]>
> I'm just looking to avoid the scenario where I add systemctl calls to
> an init script, for a package that uses the systemd D-Bus interface.
> Alternate language is solicited.
systemctl calls in init.d scripts? I do not understand.
What software we are talking about? What does it mean "uses systemd D-Bus
interface"? Does it mean that it can't do what it is supposed to do when
pid1 != systemd?
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).
--
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.
Reply to: