Breaks/Conflicts should not be used unless necessary

State explicitly that Breaks and Conflicts should only be used where
needed, and should not be used if two packages merely provide similar
functionality.

diff --git a/policy.sgml b/policy.sgml
index bad28af4257fb481693ce342af8a6b13fffdc4db..efda2a100d307fa889a75d7b7add76c872779295 100644 (file)
--- a/policy.sgml
+++ b/policy.sgml
@@ -4777,6 +4777,15 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
          example, <ref id="binaries">.
        </p>
 
+       <p>
+         Neither <tt>Breaks</tt> nor <tt>Conflicts</tt> should be used
+         unless two packages cannot be installed at the same time or
+         installing them both causes one of them to be broken or
+         unusable.  Having similar functionality or performing the same
+         tasks as another package is not sufficient reason to
+         declare <tt>Breaks</tt> or <tt>Conflicts</tt> with that package.
+       </p>
+
        <p>
          A <tt>Conflicts</tt> entry may have an "earlier than" version
          clause if the reason for the conflict is corrected in a later