X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=0121da51069c18300781f282e9440ebc46b88f55;hb=e18112ef9344084f6d050df6073468f7daf1606f;hp=b3c5886131b975c4ab1862746487e5de52d552a7;hpb=4f24058d5be9b9f5376cda90e4c03e66690ea6dd;p=debian%2Fdebian-policy.git

diff --git a/policy.sgml b/policy.sgml
index b3c5886..0121da5 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -2704,7 +2704,7 @@ Package: libc6
 	<p>
 	  This file consists of a single paragraph, possibly surrounded by
 	  a PGP signature. The fields of that paragraph are listed below.
-	  Their syntax is described above, in <ref id="pkg-controlfields">.
+	  Their syntax is described above, in <ref id="controlsyntax">.
 
 	<list compact="compact">
 	  <item><qref id="f-Format"><tt>Format</tt></qref> (mandatory)</item>
@@ -6169,11 +6169,11 @@ install -m644 debian/shlibs.<var>package</var> debian/<var>package</var>/DEBIAN/
 	  <heading>File System Structure</heading>
 
 	  <p>
-	    The location of all installed files and directories must
-	    comply with the Filesystem Hierarchy Standard (FHS),
-	    version 2.3, with the exceptions noted below, and except
-	    where doing so would violate other terms of Debian
-	    Policy.  The following exceptions to the FHS apply:
+	    The location of all files and directories must comply with the
+	    Filesystem Hierarchy Standard (FHS), version 2.3, with the
+	    exceptions noted below, and except where doing so would
+	    violate other terms of Debian Policy.  The following
+	    exceptions to the FHS apply:
 
             <enumlist>
               <item>
@@ -7968,10 +7968,12 @@ fname () {
 	<p>
 	  You may wish to restrict your script to SUSv3 features plus the
 	  above set when possible so that it may use <file>/bin/sh</file>
-	  as its interpreter. If your script works with <prgn>dash</prgn>
-	  (originally called <prgn>ash</prgn>), it probably complies with
-	  the above requirements, but if you are in doubt, use
-	  <file>/bin/bash</file>.
+	  as its interpreter.  Checking your script
+	  with <prgn>checkbashisms</prgn> from
+	  the <package>devscripts</package> package or running your script
+	  with <prgn>posh</prgn> may help uncover violations of the above
+	  requirements.  If in doubt whether a script complies with these
+	  requirements, use <file>/bin/bash</file>.
 	</p>
 
 	<p>