wrapping up #87510

Author: joy
Date: 2003/02/05 14:13:59
wrapping up #87510

git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-175

diff --git a/debian/changelog b/debian/changelog
index a2fdd7fe66b137d685a28db8a7ff46b83f737498..4d0be9e7957d0247065fe0cafdfb5cb81b74967a 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -14,6 +14,15 @@ debian-policy (3.5.9.0) unstable; urgency=low
     fixes the bug with potato, and even if it doesn't, I don't care :)
     closes #103459.
   * Fixed typos in the debconf spec noticed by Jay Bonci, closes: #178455.
+  * Clarified that using Build-Depends for build-dependencies is not a "may"
+    but a "should", added proper linking among various sections dealing with
+    the dependencies so that there is no confusion, closes: #87510.
+    If any one of those poor, misguided people ;) still thinks that the
+    requirement should be a "must" (in _our_ meaning, not RFC "MUST"),
+    please file a new bug, as it's quite unproductive to have to sift
+    through a 152-page bug log which mostly goes back-and-forth with
+    explanations how policy should work, occasionally sprinkled with
+    offtopic stuff, too.
 
  -- 
 

diff --git a/policy.sgml b/policy.sgml
index c889fdd7d6aeb5f85901e73aa35625ed3a8b36b2..d73dc6f56f0e1032249387208185f85506ae2cff 100644 (file)
--- a/policy.sgml
+++ b/policy.sgml
@@ -1262,7 +1262,7 @@
        </sect1>
 
 
-       <sect1>
+       <sect1 id="pkg-relations">
          <heading>Package relationships</heading>
 
          <p>
@@ -1349,6 +1349,10 @@
            are properly satisfied.
          </p>
 
+         <p>
+           <ref id="relationships"> explains the technical details.
+         </p>
+
        <sect1>
          <heading>Changes to the upstream sources</heading>
 
@@ -3116,34 +3120,6 @@ Package: libc6
     <chapt id="relationships"><heading>Declaring relationships between
        packages</heading>
 
-      <p>
-       Packages can declare in their control file that they have
-       certain relationships to other packages - for example, that
-       they may not be installed at the same time as certain other
-       packages, and/or that they depend on the presence of others,
-       or that they should overwrite files in certain other packages
-       if present.
-      </p>
-
-      <p>
-       This is done using the <tt>Depends</tt>, <tt>Pre-Depends</tt>,
-       <tt>Recommends</tt>, <tt>Suggests</tt>, <tt>Enhances</tt>,
-       <tt>Conflicts</tt>, <tt>Provides</tt> and <tt>Replaces</tt>
-       control file fields.
-      </p>
-
-      <p>
-        Source packages may declare relationships to binary packages,
-        saying that they require certain binary packages to be
-        installed or absent at the time of building the package.
-      </p>
-
-      <p>
-        This is done using the <tt>Build-Depends</tt>,
-        <tt>Build-Depends-Indep</tt>, <tt>Build-Conflicts</tt> and
-        <tt>Build-Conflicts-Indep</tt> control file fields.
-      </p>
-
       <sect id="depsyntax"><heading>Syntax of relationship fields
        </heading>
 
@@ -3250,6 +3226,19 @@ Build-Depends: kernel-headers-2.2.10 [!hurd-i386],
           <tt>Pre-Depends</tt>
        </heading>
 
+        <p>
+          Packages can declare in their control file that they have
+          certain relationships to other packages - for example, that
+          they may not be installed at the same time as certain other
+          packages, and/or that they depend on the presence of others.
+        </p>
+  
+        <p>
+          This is done using the <tt>Depends</tt>, <tt>Pre-Depends</tt>,
+          <tt>Recommends</tt>, <tt>Suggests</tt>, <tt>Enhances</tt> and
+          <tt>Conflicts</tt> control file fields.
+        </p>
+
        <p>
          These five fields are used to declare a dependency
          relationship by one package on another.  Except for
@@ -3539,8 +3528,10 @@ Provides: bar
          packages - <tt>Replaces</tt></heading>
 
        <p>
-         The <tt>Replaces</tt> control file field has two distinct
-         purposes, which come into play in different situations.
+          Packages can declare in their control file that they should
+          overwrite files in certain other packages, or completely
+          replace other packages. The <tt>Replaces</tt> control file
+          field has these two distinct purposes.
        </p>
 
        <sect1><heading>Overwriting files in other packages</heading>
@@ -3630,13 +3621,24 @@ Replaces: mail-transport-agent
          <tt>Build-Conflicts</tt>, <tt>Build-Conflicts-Indep</tt>
        </heading>
 
+       <p>
+          Source packages that require certain binary packages to be
+          installed or absent at the time of building the package
+          can declare relationships to those binary packages.
+        </p>
+  
+        <p>
+          This is done using the <tt>Build-Depends</tt>,
+          <tt>Build-Depends-Indep</tt>, <tt>Build-Conflicts</tt> and
+          <tt>Build-Conflicts-Indep</tt> control file fields.
+        </p>
+
         <p>
-          A source package may declare a dependency or a conflict on a
-          binary package, indicating which packages are required to be
-          present on the system in order to build the binary packages
-          from the source package.  This is done with the control file
-          fields <tt>Build-Depends</tt>, <tt>Build-Depends-Indep</tt>,
-          <tt>Build-Conflicts</tt> and <tt>Build-Conflicts-Indep</tt>.
+          Build-dependencies on "build-essential" binary packages can be
+          omitted. Please see <ref id="pkg-relations"> for more information.
+       </p>
+
+       <p>
           The dependencies and conflicts they define must be satisfied
           (as defined earlier for binary packages) in order to invoke
           the targets in <tt>debian/rules</tt>, as follows:<footnote>

diff --git a/upgrading-checklist.html b/upgrading-checklist.html
index 9b9e98b3b5a56f3cd6a4c49aae6666f752098131..23f8067a3c373b2d7da68d3bf43ceba7fb408eb1 100644 (file)
--- a/upgrading-checklist.html
+++ b/upgrading-checklist.html
@@ -57,6 +57,9 @@ picking your way through this list.
 
      - The section describing the Description: package filed once again has
        full details of the long description format. [5.7.2]
+     - Clarified that if a package has non-build-essential
+       build-dependencies, it should have them listed in the Build-Depends
+       and related fields (i.e. it's just optional). [2.4.2]
 
 3.5.8.0                    Nov 02