Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required
On Tue, Jul 23, 2019 at 2:10 PM Sean Whitton <spwhitton@spwhitton.name> wrote:
>
> The Policy Editors have decided that dropping the requirement to ship
> init scripts is not something that can be decided by means of the Policy
> Changes Process, at least for the time being.
>
> In proposing and reviewing wording to resolve this bug, then, we should
> be careful not to weaken the requirement to ship init scripts.
> Otherwise, in resolving this bug we would be changing the requirements
> to ship init scripts by means of the Policy Changes Process.
>
> I'm suggesting this be kept in mind. It need not result in a wordier
> change, and I certainly agree with you that we should assume good faith
> on the part of package maintainers.
>
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?
--
AE0D BF5A 92A5 ADE4 9481 BA6F 8A31 71EF 3661 50CE
From 5b99099d370b6304cadaedc99d5f8d8cd3063c71 Mon Sep 17 00:00:00 2001
From: David Steele <steele@debian.org>
Date: Sun, 22 Sep 2019 15:53:12 -0400
Subject: [PATCH] Clarify exception to sysv init script requirement
---
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..41f06fa 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. Also excepted are packages which require a
+feature of an alternate init system which is not available in SysV-Style
+init systems.
.. _s-upstart:
--
2.23.0
Reply to: