X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=9ad47d5dac518cf3052e5e39f0383d32fa1f5a60;hb=6bdc982dafc8714fd06349b68e05c25b0cd38001;hp=55a33babc918a6b717950f6ae4a10f3026c7ebfe;hpb=2336a1cf44bf5c0cf4b1c2d1847098a79a548a74;p=debian%2Fdebian-policy.git

diff --git a/policy.sgml b/policy.sgml
index 55a33ba..9ad47d5 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -8215,22 +8215,6 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
 	<sect1>
 	  <heading>Sharing configuration files</heading>
 
-	  <p>
-	    Packages which specify the same file as a
-	    <tt>conffile</tt> must be tagged as <em>conflicting</em>
-	    with each other.  (This is an instance of the general rule
-	    about not sharing files.  Note that neither alternatives
-	    nor diversions are likely to be appropriate in this case;
-	    in particular, <prgn>dpkg</prgn> does not handle diverted
-	    <tt>conffile</tt>s well.)
-	  </p>
-
-	  <p>
-	    The maintainer scripts must not alter a <tt>conffile</tt>
-	    of <em>any</em> package, including the one the scripts
-	    belong to.
-	  </p>
-
 	  <p>
 	    If two or more packages use the same configuration file
 	    and it is reasonable for both to be installed at the same
@@ -8280,6 +8264,34 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
 	    and which manages the shared configuration files.  (The
 	    <tt>sgml-base</tt> package is a good example.)
 	  </p>
+
+	  <p>
+	    If the configuration file cannot be shared as described above,
+	    the packages must be marked as conflicting with each other.
+	    Two packages that specify the same file as
+	    a <tt>conffile</tt> must conflict.  This is an instance of the
+	    general rule about not sharing files.  Neither alternatives
+	    nor diversions are likely to be appropriate in this case; in
+	    particular, <prgn>dpkg</prgn> does not handle diverted
+	    <tt>conffile</tt>s well.
+	  </p>
+
+	  <p>
+	    When two packages both declare the same <tt>conffile</tt>, they
+	    may see left-over configuration files from each other even
+	    though they conflict with each other.  If a user removes
+	    (without purging) one of the packages and installs the other,
+	    the new package will take over the <tt>conffile</tt> from the
+	    old package.  If the file was modified by the user, it will be
+	    treated the same as any other locally
+	    modified <tt>conffile</tt> during an upgrade.
+	  </p>
+
+	  <p>
+	    The maintainer scripts must not alter a <tt>conffile</tt>
+	    of <em>any</em> package, including the one the scripts
+	    belong to.
+	  </p>
 	</sect1>
 
 	<sect1>