Bug#835490: debian-policy: remove references to upstart
Package: debian-policy
Severity: normal
Upstart is no longer part of Debian[1] nor actively maintained
upstream. Policy should drop references to it as an alternative init
system.
I've attached a patch to remove section 9.11.1 (actually to replace it
with an empty stub to ensure there is no section 9.11.1 with different
contents in the future).
Ansgar
[1] <https://bugs.debian.org/808289>
diff --git a/policy.sgml b/policy.sgml
index 9cd182b..3c75da9 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -8553,47 +8553,8 @@ exec /usr/lib/foo/foo "$@"
scripts and may not have a one-to-one correspondence with the init
scripts.
</p>
- <sect1 id="upstart">
- <heading>Event-based boot with upstart</heading>
-
- <p>
- Packages may integrate with the <prgn>upstart</prgn> event-based
- boot system by installing job files in the
- <file>/etc/init</file> directory. SysV init scripts for which
- an equivalent upstart job is available must query the output of
- the command <prgn>initctl version</prgn> for the string
- <tt>upstart</tt> and avoid running in favor of the native
- upstart job, using a test such as this:
- <example compact="compact">
-if [ "$1" = start ] && which initctl >/dev/null && initctl version | grep -q upstart
-then
- exit 1
-fi
- </example>
- </p>
- <p>
- Because packages shipping upstart jobs may be installed on
- systems that are not using upstart, maintainer scripts must
- still use the common <prgn>update-rc.d</prgn> and
- <prgn>invoke-rc.d</prgn> interfaces for configuring runlevels
- and for starting and stopping services. These maintainer
- scripts must not call the upstart <prgn>start</prgn>,
- <prgn>restart</prgn>, <prgn>reload</prgn>, or <prgn>stop</prgn>
- interfaces directly. Instead, implementations of
- <prgn>invoke-rc.d</prgn> must detect when upstart is running and
- when an upstart job with the same name as an init script is
- present, and perform the requested action using the upstart job
- instead of the init script.
- </p>
- <p>
- Dependency-based boot managers for SysV init scripts, such as
- <prgn>startpar</prgn>, may avoid running a given init script
- entirely when an equivalent upstart job is present, to avoid
- unnecessary forking of no-op init scripts. In this case, the
- boot manager should integrate with upstart to detect when the
- upstart job in question is started or stopped to know when the
- dependency has been satisfied.
- </p>
+ <sect1>
+ <heading>(removed)</heading>
</sect1>
</sect>
Reply to: