Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required
- To: Sean Whitton <spwhitton@spwhitton.name>
- Cc: 932704@bugs.debian.org, David Steele <steele@debian.org>
- Subject: Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required
- From: Dmitry Bogatov <KAction@disroot.org>
- Date: Tue, 01 Oct 2019 22:43:41 +0000
- Message-id: <[🔎] 20191001224228.DE3BA2D76C@disroot.org>
- Reply-to: Dmitry Bogatov <KAction@disroot.org>, 932704@bugs.debian.org
- In-reply-to: <87blv4e4hz.fsf@iris.silentflame.com>
- References: <8736iy72os.fsf@iris.silentflame.com> <e083aae3ba2ede4487700c6eede9691f14588a52.camel@43-1.org> <87k1c8947a.fsf@athena.silentflame.com> <CAOHcdNYtuYdxWQukuXbnLkQSKNe6Wbkaca6H-q_X+L_XTjDAVQ@mail.gmail.com> <87a7d4fwqp.fsf@iris.silentflame.com> <CAOHcdNY+Pk69BtUV42O9KOTDYshXq_c5SkEfso+9CZ7g62U3ww@mail.gmail.com> <CAOHcdNZgfVpddNy-R9L=fbbTwDdmKDamPnhX-T60S=Jwm-DKvg@mail.gmail.com> <20190925154318.3055D20860@disroot.org> <CAOHcdNZHvSULJguYZP-R5Qej-_8MW2ZSiOq6dk_G7SToJre98w@mail.gmail.com> <CAOHcdNY+Pk69BtUV42O9KOTDYshXq_c5SkEfso+9CZ7g62U3ww@mail.gmail.com> <20190926152637.7505C21ADF@disroot.org> <CAOHcdNY+Pk69BtUV42O9KOTDYshXq_c5SkEfso+9CZ7g62U3ww@mail.gmail.com> <f00034795869e8559bb2fd536a0299c252dc90ca.camel@43-1.org> <CAOHcdNY+Pk69BtUV42O9KOTDYshXq_c5SkEfso+9CZ7g62U3ww@mail.gmail.com> <20190928161844.CEEC823BA4@disroot.org> <87blv4e4hz.fsf@iris.silentflame.com> <CAOHcdNY+Pk69BtUV42O9KOTDYshXq_c5SkEfso+9CZ7g62U3ww@mail.gmail.com>
[2019-09-28 10:04] Sean Whitton <spwhitton@spwhitton.name>
> Hello,
>
> On Sat 28 Sep 2019 at 04:18PM +00, Dmitry Bogatov wrote:
>
> > 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.
>
> I think this would work. What do you think, David?
>
> Dmitry, perhaps you could work up a patch against policy.git.
From 629b6fd334806e5389e3cfee44997d95ac96501c Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov <KAction@debian.org>
Date: Sun, 29 Sep 2019 18:53:36 +0000
Subject: [PATCH] Policy: Allow missing init.d script for services, specific to other init
Wording: Dmitry Bogatov <kaction@disroot.org>
Closes: #932704
---
policy/ch-opersys.rst | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/policy/ch-opersys.rst b/policy/ch-opersys.rst
index 3e685cf..309d6fe 100644
--- 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.
.. _s-upstart:
--
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: