X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=9479fc9d5ef3269fcdcbfdbae965a9d8b59217b8;hb=73edbbc37d79bb9c3c6069c957c2bf7500fc1926;hp=73d5d8fc5a10a2163fe5a9b9a2354a575b370257;hpb=c07945c953c57092190bd7cf9594dd59a46fe0e7;p=debian%2Fdebian-policy.git

diff --git a/policy.sgml b/policy.sgml
index 73d5d8f..9479fc9 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -8038,33 +8038,27 @@ Reloading <var>description</var> configuration...done.
 	</p>
 
 	<p>
-	  Packages which provide the ability to view/show/play,
-	  compose, edit or print MIME types should register themselves
-	  as such following the current MIME support policy.
+	  Packages which provide programs to view/show/play, compose, edit or
+	  print MIME types should register them as such by placing a file in
+	  <manref name="mailcap" section="5"> format (RFC 1524) in the directory
+	  <file>/usr/lib/mime/packages/</file>.  The file name should be the
+	  binary package's name.
 	</p>
 
 	<p>
 	  The <package>mime-support</package> package provides the
-	  <prgn>update-mime</prgn> program which allows packages to
-	  register programs that can show, compose, edit or print
-	  MIME types.
-	</p>
-
-	<p>
-	  Packages containing such programs must register them
-	  with <prgn>update-mime</prgn> as documented in <manref
-	  name="update-mime" section="8">. They should <em>not</em> depend
-	  on, recommend, or suggest <prgn>mime-support</prgn>. Instead,
-	  they should just put something like the following in the
-	  <tt>postinst</tt> and <tt>postrm</tt> scripts:
-
-	  <example>
-  if [ -x /usr/sbin/update-mime ]; then
-      update-mime
-  fi
-	  </example>
+	  <prgn>update-mime</prgn> program, which integrates these
+	  registrations in the <file>/etc/mailcap</file> file, using Dpkg
+	  triggers<footnote>
+	    Creating, modifying or removing a file in
+	    <file>/usr/lib/mime/packages/</file> using maintainer scripts will
+	    not activate the trigger.  In that case, it can be done by calling
+	    <tt>dpkg-trigger --no-await --by-package=&lt;me&gt; /usr/lib/mime/packages</tt>,
+	    where <tt>&lt;me&gt;</tt> is the name of the package.
+	  </footnote>.
+	  Packages using this facility <em>should not</em> depend on,
+	  recommend, or suggest <prgn>mime-support</prgn>.
 	</p>
-
       </sect>
 
       <sect>
@@ -8278,6 +8272,74 @@ exec /usr/lib/foo/foo "$@"
 	</p>
       </sect>
 
+      <sect id="alternateinit">
+        <heading>Alternate init systems</heading>
+        <p>
+          A number of other init systems are available now in Debian that
+          can be used in place of <package>sysvinit</package>.  Alternative
+          init implementations must support running SysV init scripts as
+          described at <ref id="sysvinit"> for compatibility.
+        </p>
+        <p>
+          Packages may integrate with these replacement init systems by
+          providing implementation-specific configuration information about
+          how and when to start a service or in what order to run certain
+          tasks at boot time.  However, any package integrating with other
+          init systems must also be backwards-compatible with
+          <package>sysvinit</package> by providing a SysV-style init script
+          with the same name as and equivalent functionality to any
+          init-specific job, as this is the only start-up configuration
+          method guaranteed to be 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 <file>/etc/rcS.d/</file>
+          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>
+      </sect>
+
     </chapt>