explicate that appendices aren't necessarily normative

Author: joy
Date: 2003/02/22 15:55:07
explicate that appendices aren't necessarily normative

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

diff --git a/policy.sgml b/policy.sgml
index f8e3b7db5ba9ebf271a16fe6f55927ff96b0714a..549a928be41253f855671f222b586ae1f32a1653 100644 (file)
--- a/policy.sgml
+++ b/policy.sgml
@@ -66,7 +66,6 @@
          distribution.
        </p>
 
-
        <p>
          This manual also describes Debian policy as it relates to
          creating Debian packages. It is not a tutorial on how to build
@@ -116,7 +115,13 @@
        </p>
 
        <p>
-         In this manual, the words <em>must</em>, <em>should</em> and
+         The appendices to this manual are not necessarily normative,
+         either. Please see <ref id="pkg-scope"> for more information.
+       </p>
+
+       <p>
+         In the normative part of this manual,
+         the words <em>must</em>, <em>should</em> and
          <em>may</em>, and the adjectives <em>required</em>,
          <em>recommended</em> and <em>optional</em>, are used to
          distinguish the significance of the various guidelines in