Add an id to all sect[123].

16 files changed, 135 insertions, 135 deletions

diff --git a/doc/guide/files/binary.xml b/doc/guide/files/binary.xml
index 16923fd3818..3548464b8d4 100644
--- a/doc/guide/files/binary.xml
+++ b/doc/guide/files/binary.xml
@@ -1,9 +1,9 @@
-<!-- $NetBSD: binary.xml,v 1.12 2005/05/14 22:34:59 rillig Exp $ -->
+<!-- $NetBSD: binary.xml,v 1.13 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="binary">
   <title>Creating binary packages</title>
 
-  <sect1>
+  <sect1 id="building-a-single-binary-package">
     <title>Building a single binary package</title>
 
     <para>
@@ -38,7 +38,7 @@
       such a binary package.</para>
   </sect1>
 
-  <sect1>
+  <sect1 id="settings-for-creationg-of-binary-packages">
     <title>Settings for creation of binary packages</title>
 
     <para>See <xref linkend="build.helpful-targets"/>.</para>
@@ -81,7 +81,7 @@ PKG_DEVELOPER?= yes
 _ACCEPTABLE=    yes</programlisting>
       </sect3>
 
-      <sect3>
+      <sect3 id="build.conf">
 	<title><filename>build.conf</filename></title>
 
 	<para>In <filename>pkgsrc/mk/bulk</filename>, copy
@@ -94,7 +94,7 @@ _ACCEPTABLE=    yes</programlisting>
 	  <command>cvs update</command>.</para>
       </sect3>
 
-      <sect3>
+      <sect3 id="pre-build.local">
 	<title><filename>pre-build.local</filename></title>
 
 	<para>It is possible to configure the bulk build to perform
@@ -114,7 +114,7 @@ _ACCEPTABLE=    yes</programlisting>
       </sect3>
     </sect2>
 
-    <sect2>
+    <sect2 id="other-environmental-considerations">
       <title>Other environmental considerations</title>
 
       <para>As <filename>/usr/pkg</filename> will be completely
@@ -140,7 +140,7 @@ fi</programlisting>
 	gets rebooted or crashes. You have been warned! :)</para>
     </sect2>
 
-    <sect2>
+    <sect2 id="operation">
       <title>Operation</title>
 
       <para>Make sure you don't need any of the packages still
@@ -173,7 +173,7 @@ fi</programlisting>
       </para> 
     </sect2>
 
-    <sect2>
+    <sect2 id="what-it-does">
       <title>What it does</title>
 
       <para>The bulk builds consist of three steps:</para>
@@ -231,7 +231,7 @@ fi</programlisting>
       </para> 
     </sect2>
 
-    <sect2>
+    <sect2 id="disk-space-requirements">
       <title>Disk space requirements</title>
 
       <para>Currently, roughly the following requirements are valid for
@@ -267,7 +267,7 @@ fi</programlisting>
       </para> 
     </sect2>
 
-    <sect2>
+    <sect2 id="setting-up-a-sandbox">
       <title>Setting up a sandbox for chroot'ed builds</title>
 
       <para>
@@ -403,7 +403,7 @@ fi</programlisting>
         (wherever that points/mounts to/from).</para>
     </sect2>
 
-    <sect2>
+    <sect2 id="building-a-partial-set">
       <title>Building a partial set of packages</title>
 
       <para> In addition to building a complete set of all packages in
@@ -555,7 +555,7 @@ nbftp% <userinput>chmod 755 .</userinput> </screen>
     </sect2>
   </sect1>
 
-  <sect1>
+  <sect1 id="creating-cdroms">
     <title>Creating a multiple CD-ROM packages collection</title>
 
     <para>
@@ -569,7 +569,7 @@ nbftp% <userinput>chmod 755 .</userinput> </screen>
       package.
     </para>
 
-    <sect2>
+    <sect2 id="cdpack-example">
       <title>Example of cdpack</title>
 
       <para>
diff --git a/doc/guide/files/build.xml b/doc/guide/files/build.xml
index 5a1c4f98fa3..5921ab9124c 100644
--- a/doc/guide/files/build.xml
+++ b/doc/guide/files/build.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: build.xml,v 1.6 2005/05/24 11:11:24 rillig Exp $ -->
+<!-- $NetBSD: build.xml,v 1.7 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="build">
   <title>The build process</title>
@@ -127,7 +127,7 @@ CONFIGURE_ARGS+=        --with-guile-prefix=${LOCALBASE}        \
     </itemizedlist>
   </sect1>
 
-  <sect1>
+  <sect1 id="main-targets">
     <title>Main targets</title>
 
     <para>The main targets used during the build process defined in
diff --git a/doc/guide/files/buildlink.xml b/doc/guide/files/buildlink.xml
index a08d344194c..0d5030a7cce 100644
--- a/doc/guide/files/buildlink.xml
+++ b/doc/guide/files/buildlink.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: buildlink.xml,v 1.3 2005/05/14 22:34:59 rillig Exp $ -->
+<!-- $NetBSD: buildlink.xml,v 1.4 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="buildlink">
   <title>Buildlink methodology</title>
@@ -33,7 +33,7 @@
     designed to insulate the package build from non-system-supplied
     software. </para>
 
-  <sect1>
+  <sect1 id="converting-to-buildlink3">
     <title>Converting packages to use buildlink3</title>
 
     <para>The process of converting packages to use the buildlink3
@@ -137,7 +137,7 @@
       description of how to use them properly.</para>
   </sect1>
 
-  <sect1>
+  <sect1 id="creating-buildlink3.mk">
     <title>Writing <filename>buildlink3.mk</filename> files</title>
 
     <para> A package's <filename>buildlink3.mk</filename> file is
@@ -158,7 +158,7 @@
     <screen>&cprompt; <userinput>cd pkgsrc/<replaceable>category</replaceable>/<replaceable>pkgdir</replaceable>
 &cprompt; createbuildlink -3 &gt;buildlink3.mk</userinput></screen> 
 
-    <sect2>
+    <sect2 id="anatomy-of-bl3">
       <title>Anatomy of a buildlink3.mk file</title>
 
       <para>The following real-life example
@@ -343,7 +343,7 @@ BUILDLINK_DEPTH:=       ${BUILDLINK_DEPTH:S/+$//} </programlisting>
 	    </para>
     </sect2>
 
-    <sect2>
+    <sect2 id="updating-buildlink-depends">
       <title>Updating <varname>BUILDLINK_DEPENDS.<replaceable>pkg</replaceable></varname> in <filename>buildlink3.mk</filename> files</title>
 
       <para>
@@ -388,7 +388,7 @@ BUILDLINK_DEPTH:=       ${BUILDLINK_DEPTH:S/+$//} </programlisting>
     </sect2>
   </sect1>
 
-  <sect1>
+  <sect1 id="writing-builtin.mk">
     <title>Writing <filename>builtin.mk</filename> files</title>
 
     <para>
@@ -429,7 +429,7 @@ BUILDLINK_DEPTH:=       ${BUILDLINK_DEPTH:S/+$//} </programlisting>
       </listitem>
     </orderedlist>
 
-    <sect2>
+    <sect2 id="anatomy-of-builtin.mk">
       <title>Anatomy of a <filename>builtin.mk</filename> file</title>
 
       <para>The following is the recommended template for builtin.mk
@@ -527,7 +527,7 @@ CHECK_BUILTIN.foo?=     no
         </para> 
     </sect2>
     
-    <sect2>
+    <sect2 id="native-or-pkgsrc-preference">
       <title>Global preferences for native or pkgsrc software</title>
 
       <para>
diff --git a/doc/guide/files/components.xml b/doc/guide/files/components.xml
index faea90e52ef..b86d0d4be59 100644
--- a/doc/guide/files/components.xml
+++ b/doc/guide/files/components.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: components.xml,v 1.7 2005/05/15 20:24:17 rillig Exp $ -->
+<!-- $NetBSD: components.xml,v 1.8 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="components"> <?dbhtml filename="components.html"?>
   <title>Package components - files, directories and contents</title>
@@ -268,7 +268,7 @@ converters    games         mbone         print         x11</programlisting>
       <emphasis>they are applied after pkgsrc patches are applied</emphasis>.</para>
   </sect1>
 
-  <sect1>
+  <sect1 id="other-mandatory-files">
     <title>Other mandatory files</title>
 
     <variablelist>
@@ -350,7 +350,7 @@ converters    games         mbone         print         x11</programlisting>
     </variablelist>
   </sect1>
 
-  <sect1>
+  <sect1 id="work-dir">
     <title><filename>work*</filename></title>
 
     <para>When you type <command>make</command> the distribution files are
@@ -385,7 +385,7 @@ converters    games         mbone         print         x11</programlisting>
       <filename>work.sparc</filename>. </para>
   </sect1>
 
-  <sect1>
+  <sect1 id="files-dir">
     <title><filename>files/*</filename></title>
 
     <para>If you have any files that you wish to be placed in the package prior
diff --git a/doc/guide/files/editing.xml b/doc/guide/files/editing.xml
index 7ff227758af..ddf471077d4 100644
--- a/doc/guide/files/editing.xml
+++ b/doc/guide/files/editing.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: editing.xml,v 1.6 2005/05/07 22:28:47 wiz Exp $ -->
+<!-- $NetBSD: editing.xml,v 1.7 2005/05/24 12:14:42 wiz Exp $ -->
 
 <appendix id="editing">
   <title>Editing guidelines for the pkgsrc guide</title>
@@ -8,7 +8,7 @@
     itself.
   </para>
 
-  <sect1>
+  <sect1 id="targets">
     <title>Targets</title>
   
     <para>
@@ -56,7 +56,7 @@
     </itemizedlist>
   </sect1>
 
-  <sect1>
+  <sect1 id="procedure">
     <title>Procedure</title>
     
     <para>
diff --git a/doc/guide/files/examples.xml b/doc/guide/files/examples.xml
index 962375bb038..09b34ed8667 100644
--- a/doc/guide/files/examples.xml
+++ b/doc/guide/files/examples.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: examples.xml,v 1.4 2005/05/14 22:34:59 rillig Exp $ -->
+<!-- $NetBSD: examples.xml,v 1.5 2005/05/24 12:14:42 wiz Exp $ -->
 
 <appendix id="examples">
   <title>A simple example package: bison</title>
@@ -9,10 +9,10 @@
     present in the tree is beyond us, but it's useful for the purposes of
     this exercise.</para>
 
-  <sect1>
+  <sect1 id="example-files">
     <title>files</title>
 
-    <sect2>
+    <sect2 id="example-Makefile">
       <title>Makefile</title>
 
       <programlisting># &#36;NetBSD&#36;
@@ -32,7 +32,7 @@ INFO_FILES=     bison.info
 .include "../../mk/bsd.pkg.mk"</programlisting>
     </sect2>
 
-    <sect2>
+    <sect2 id="example-descr">
       <title>DESCR</title>
 
       <programlisting>GNU version of yacc.  Can make re-entrant parsers, and numerous other
@@ -40,7 +40,7 @@ improvements.  Why you would want this when Berkeley &man.yacc.1; is part
 of the &os; source tree is beyond me.</programlisting>
     </sect2>
 
-    <sect2>
+    <sect2 id="example-plist">
       <title>PLIST</title>
 
       <programlisting>@comment &#36;NetBSD&#36;
@@ -50,7 +50,7 @@ share/bison.simple
 share/bison.hairy</programlisting>
     </sect2>
 
-    <sect2>
+    <sect2 id="checking-package-with-pkglint">
       <title>Checking a package with <command>pkglint</command></title>
 
       <para>The NetBSD package system comes with <pkg>pkgtools/pkglint</pkg>
@@ -68,7 +68,7 @@ looks fine.</screen>
     </sect2>
   </sect1>
 
-  <sect1>
+  <sect1 id="steps-for-b-i-p">
     <title>Steps for building, installing, packaging</title>
 
     <para>Create the directory where the package lives,
diff --git a/doc/guide/files/faq.xml b/doc/guide/files/faq.xml
index 25570240e1c..a61ef926470 100644
--- a/doc/guide/files/faq.xml
+++ b/doc/guide/files/faq.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: faq.xml,v 1.9 2005/05/15 20:27:15 rillig Exp $ -->
+<!-- $NetBSD: faq.xml,v 1.10 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="faq"> <?dbhtml filename="faq.html"?>
   <title>Frequently Asked Questions</title>
@@ -8,7 +8,7 @@
     previous chapters, and it contains items for both pkgsrc users and
     developers. </para>
 
-  <sect1>
+  <sect1 id="mailing-list-pointers">
     <title>Are there any mailing lists for pkg-related discussion?</title>
 
     <para>
@@ -60,7 +60,7 @@
 </sect1>
 
 
-<sect1>
+<sect1 id="pkgviews-docs">
     <title>Where's the pkgviews documentation?</title>
 
     <para> Pkgviews is tightly integrated with buildlink. You can find a 
@@ -229,7 +229,7 @@
 </sect1>
 
 
-<sect1>
+<sect1 id="non-root-pkgsrc">
     <title>How to use pkgsrc as non-root</title>
     
      <para>  If you want to use pkgsrc as non-root user, you can set
@@ -239,7 +239,7 @@
       message</ulink> for more details.  </para> 
 </sect1>
 
-<sect1>
+<sect1 id="resume-transfers">
     <title>How to resume transfers when fetching distfiles?</title>
 
     <para>By default resuming transfers in pkgsrc is disabled, but you
@@ -264,7 +264,7 @@
 
 </sect1>
 
-<sect1>
+<sect1 id="XFree86-from-pkgsrc">
     <title>How can I install/use XFree86 from pkgsrc?</title>
 
     <para> If you want to use XFree86 from pkgsrc instead of your
@@ -279,7 +279,7 @@
 </sect1>
 
 
-<sect1>
+<sect1 id="x.org-from-pkgsrc">
     <title>How can I install/use X.org from pkgsrc?</title>
 
     <para> If you want to use X.org from pkgsrc instead of your system's
@@ -293,7 +293,7 @@
 </sect1>
 
 
-<sect1>
+<sect1 id="fetch-behind-firewall">
     <title>How to fetch files from behind a firewall</title>
 
     <para> If you are sitting behind a firewall which does not allow
@@ -309,7 +309,7 @@ http_proxy=http://orpheus.amdahl.com:80/</programlisting>
 </sect1>
 
     
-<sect1>
+<sect1 id="passive-ftp">
     <title>How do I tell <command>make fetch</command> to do passive FTP?</title>
 
     <para> This depends on which utility is used to retrieve distfiles. From <filename>bsd.pkg.mk</filename>, <varname>FETCH_CMD</varname> is assigned the first available command from the following list: </para>
@@ -330,7 +330,7 @@ http_proxy=http://orpheus.amdahl.com:80/</programlisting>
 </sect1>
 
     
-<sect1>
+<sect1 id="fetching-all-distfiles">
     <title>How to fetch all distfiles at once</title>
 
     <para> You would like to download all the distfiles in a single
@@ -378,7 +378,7 @@ http_proxy=http://orpheus.amdahl.com:80/</programlisting>
 </sect1>
 
 
-<sect1>
+<sect1 id="tmac.andoc-missing">
     <title>What does <quote>Don't know how to make /usr/share/tmac/tmac.andoc</quote> mean?</title>
 
     <para> When compiling the <pkg>pkgtools/pkg_install</pkg> package,
@@ -396,7 +396,7 @@ http_proxy=http://orpheus.amdahl.com:80/</programlisting>
 </sect1>
 
 
-<sect1>
+<sect1 id="bsd.own.mk-missing">
     <title>What does <quote>Could not find bsd.own.mk</quote> mean?</title>
 
     <para> You didn't install the compiler set,
@@ -413,7 +413,7 @@ http_proxy=http://orpheus.amdahl.com:80/</programlisting>
 </sect1>
 
 
-<sect1>
+<sect1 id="using-sudo-with-pkgsrc">
     <title>Using 'sudo' with pkgsrc</title>
 
     <para>
diff --git a/doc/guide/files/fixes.xml b/doc/guide/files/fixes.xml
index bcb79f3dd61..f99bc8b5a37 100644
--- a/doc/guide/files/fixes.xml
+++ b/doc/guide/files/fixes.xml
@@ -1,12 +1,12 @@
-<!-- $NetBSD: fixes.xml,v 1.14 2005/05/14 22:34:59 rillig Exp $ -->
+<!-- $NetBSD: fixes.xml,v 1.15 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="fixes"> <?dbhtml filename="fixes.html"?>
   <title>Notes on fixes for packages</title>
 
-  <sect1>
+  <sect1 id="general-operation">
     <title>General operation</title>
 
-    <sect2>
+    <sect2 id="pulling-vars-from-etc-mk.conf">
       <title>How to pull in variables from /etc/mk.conf</title>
     
       <para> The problem with package-defined variables that can be
@@ -45,7 +45,7 @@
     </sect2>
 
 
-    <sect2>
+    <sect2 id="restricted-packages">
       <title>Restricted packages</title>
     
       <para> Some licenses restrict how software may be re-distributed.
@@ -269,7 +269,7 @@
     </sect2>
 
 
-    <sect2>
+    <sect2 id="conflicts">
       <title>Handling conflicts with other packages</title>
     
       <para> Your package may conflict with other packages a user might
@@ -300,7 +300,7 @@
     </sect2>
 
 
-    <sect2>
+    <sect2 id="not-building-packages">
       <title>Packages that cannot or should not be built</title>
     
       <para>
@@ -324,7 +324,7 @@
     </sect2>
     
     
-    <sect2>
+    <sect2 id="undeletable-packages">
       <title>Packages which should not be deleted, once installed</title>
     
       <para>To ensure that a package may not be deleted, once it has been
@@ -362,7 +362,7 @@
     </sect2>
 
 
-    <sect2>
+    <sect2 id="compiler-bugs">
       <title>How to handle compiler bugs</title>
     
       <para>  Some source files trigger bugs in the compiler, based on
@@ -380,7 +380,7 @@
     </sect2>
             
 
-    <sect2>
+    <sect2 id="bumping-pkgrevision">
       <title>How to handle incrementing versions when fixing an existing package</title>
     
       <para> When making fixes to an existing package it can be useful
@@ -406,7 +406,7 @@
     </sect2>
     
     
-    <sect2>
+    <sect2 id="portability-of-packages">
       <title>Portability of packages</title>
 
       <para>One appealing feature of pkgsrc is that it runs on many different
@@ -414,7 +414,7 @@
         that packages in pkgsrc are portable. There are some particular
         details you should pay attention to while working on pkgsrc.</para>
 
-      <sect3>
+      <sect3 id="install-scripts">
         <title>${INSTALL}, ${INSTALL_DATA_DIR}, ...</title>
 
         <para>The BSD-compatible <command>install</command> supplied with some
@@ -429,10 +429,10 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2</programlisting>
   </sect1>
   
   
-  <sect1>
+  <sect1 id="downloading-issues">
     <title>Possible downloading issues</title>
 
-    <sect2>
+    <sect2 id="no-plain-download">
       <title>Packages whose distfiles aren't available for plain downloading</title>
     
       <para> If you need to download from a dynamic URL you can set
@@ -461,7 +461,7 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2</programlisting>
     </sect2>
     
 
-    <sect2>
+    <sect2 id="modified-distfiles-same-name">
       <title>How to handle modified distfiles with the 'old' name</title>
     
       <para> Sometimes authors of a software package make some
@@ -481,7 +481,7 @@ ${INSTALL_DATA_DIR} ${PREFIX}/dir2</programlisting>
   </sect1>
 
 
-  <sect1>
+  <sect1 id="configuration-gotchas">
     <title>Configuration gotchas</title>
 
     <sect2 id="fixes.libtool">
@@ -625,7 +625,7 @@ dynamic linker chooses the library with the greater REVISION number. </programli
     </sect2>
 
     
-    <sect2>
+    <sect2 id="using-libtool">
       <title>Using libtool on GNU packages that already support libtool</title>
 
       <para>Add <varname>USE_LIBTOOL=yes</varname> to the
@@ -681,7 +681,7 @@ dynamic linker chooses the library with the greater REVISION number. </programli
     </sect2>
 
     
-    <sect2>
+    <sect2 id="autoconf-automake">
       <title>GNU Autoconf/Automake</title>
 
       <para>If a package needs GNU autoconf or automake to be executed
@@ -734,10 +734,10 @@ pre-configure:
   </sect1>
   
   
-  <sect1>
+  <sect1 id="building-considerations">
     <title>Building considerations</title>
 
-    <sect2>
+    <sect2 id="cpp-defines">
       <title>CPP defines</title>
     
       <para>
@@ -768,10 +768,10 @@ pre-configure:
   </sect1>
   
   
-  <sect1>
+  <sect1 id="package-specific-actions">
     <title>Package specific actions</title>
 
-    <sect2>
+    <sect2 id="package-configuration-files">
       <title>Package configuration files</title>
       
       <para> Packages should be taught to look for their configuration
@@ -823,7 +823,7 @@ pre-configure:
           of <filename>${PREFIX}/etc</filename>. </para>
     </sect2>
 
-    <sect2>
+    <sect2 id="user-interaction">
       <title>User interaction</title>
 
       <para>Occasionally, packages require interaction from the user, and this can be
@@ -859,7 +859,7 @@ pre-configure:
     </sect2>
 
 
-    <sect2>
+    <sect2 id="handling-licenses">
       <title>Handling licenses</title>
 
       <para>A package may underly a license which the user has or has
@@ -920,7 +920,7 @@ pre-configure:
       </sect2>
     
 
-    <sect2>
+    <sect2 id="creating-accounts">
       <title>Creating an account from a package</title>
     
       <para> There are two make variables used to control the creation
@@ -960,7 +960,7 @@ pre-configure:
     </sect2>
     
     
-    <sect2>
+    <sect2 id="installing-score-files">
       <title>Installing score files</title>
     
       <para> Certain packages, most of them in the games category, install
@@ -985,7 +985,7 @@ pre-configure:
     </sect2>
     
     
-    <sect2>
+    <sect2 id="login-shells">
       <title>Packages providing login shells</title>
     
       <para>  If the purpose of the package is to provide a login shell,
@@ -1010,7 +1010,7 @@ pre-configure:
     </sect2>
     
     
-    <sect2>
+    <sect2 id="perl-scripts">
       <title>Packages containing perl scripts</title>
     
       <para>
@@ -1022,7 +1022,7 @@ pre-configure:
     </sect2>
     
     
-    <sect2>
+    <sect2 id="hardcoded-paths">
       <title>Packages with hardcoded paths to other interpreters</title>
     
       <para>
@@ -1040,7 +1040,7 @@ pre-configure:
     </sect2>
 
     
-    <sect2>
+    <sect2 id="perl-modules">
       <title>Packages installing perl modules</title>
   
       <para>Makefiles of packages providing perl5 modules should include
@@ -1140,7 +1140,7 @@ pre-configure:
     </sect2>
 
 
-    <sect2>
+    <sect2 id="gconf2-data-files">
       <title>Packages installing GConf2 data files</title>
     
       <para>
@@ -1193,7 +1193,7 @@ pre-configure:
     </sect2>
     
     
-    <sect2>
+    <sect2 id="scrollkeeper-data-files">
       <title>Packages installing scrollkeeper data files</title>
     
       <para>
@@ -1227,7 +1227,7 @@ pre-configure:
     </sect2>
     
     
-    <sect2>
+    <sect2 id="x11-fonts">
       <title>Packages installing X11 fonts</title>
     
       <para> If a package installs font files, you will need to rebuild
@@ -1250,7 +1250,7 @@ pre-configure:
     </sect2>
     
     
-    <sect2>
+    <sect2 id="gtk2-modules">
       <title>Packages installing GTK2 modules</title>
     
       <para>If a package installs gtk2 immodules or loaders, you need to
@@ -1295,7 +1295,7 @@ pre-configure:
     </sect2>
     
     
-    <sect2>
+    <sect2 id="sgml-xml-data">
       <title>Packages installing SGML or XML data</title>
     
       <para> If a package installs SGML or XML data files that need to be
@@ -1342,7 +1342,7 @@ pre-configure:
     </sect2>
     
     
-    <sect2>
+    <sect2 id="mime-database">
       <title>Packages installing extensions to the MIME database</title>
     
       <para> If a package provides extensions to the MIME database by
@@ -1384,7 +1384,7 @@ pre-configure:
     </sect2>
 
     
-    <sect2>
+    <sect2 id="intltool">
       <title>Packages using intltool</title>
     
       <para>   If a package uses intltool during its build, include the 
@@ -1400,7 +1400,7 @@ pre-configure:
     </sect2>
 
 
-    <sect2>
+    <sect2 id="startup-scripts">
         <title>Packages installing startup scripts</title>
         <para>If a package contains a rc.d script, it won't be copied into
         the startup directory by default, but you can enable it, by adding
@@ -1414,7 +1414,7 @@ pre-configure:
   </sect1>
 
     
-  <sect1>
+  <sect1 id="feedback-to-author">
     <title>Feedback to the author</title>
     
     <para> If you have found any bugs in the package you make available,
diff --git a/doc/guide/files/getting.xml b/doc/guide/files/getting.xml
index ad804b05f63..d1172afaff1 100644
--- a/doc/guide/files/getting.xml
+++ b/doc/guide/files/getting.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: getting.xml,v 1.3 2005/05/15 20:28:15 rillig Exp $ -->
+<!-- $NetBSD: getting.xml,v 1.4 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="getting">
   <title>Where to get pkgsrc</title>
@@ -6,7 +6,7 @@
   <para>There are three ways to get pkgsrc. Either as a tar file, via SUP, or
     via CVS. All three ways are described here.</para>
 
-  <sect1>
+  <sect1 id="as-tar-file">
     <title>As tar file</title>
     
     <para>To get pkgsrc going, you need to get the pkgsrc.tar.gz file
@@ -16,7 +16,7 @@
   
   </sect1>
 
-  <sect1>
+  <sect1 id="via-sup">
     <title>Via SUP</title>
     
     <para>As an alternative to the tar file, you can get pkgsrc via
@@ -31,7 +31,7 @@
       <command>sup -v <replaceable>/path/to/your/supfile</replaceable></command>.</para>
   </sect1>
 
-  <sect1>
+  <sect1 id="via-cvs">
     <title>Via CVS</title>
     
     <para>To get pkgsrc via CVS, make sure you have <quote>cvs</quote> installed.
diff --git a/doc/guide/files/introduction.xml b/doc/guide/files/introduction.xml
index fd693ba5af2..1cbf031eadf 100644
--- a/doc/guide/files/introduction.xml
+++ b/doc/guide/files/introduction.xml
@@ -1,9 +1,9 @@
-<!-- $NetBSD: introduction.xml,v 1.4 2005/05/15 20:30:54 rillig Exp $ -->
+<!-- $NetBSD: introduction.xml,v 1.5 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="introduction">
   <title>Introduction</title>
 
-  <sect1>
+  <sect1 id="introduction-section">
     <title>Introduction</title>
 
     <para> There is a lot of software freely available for Unix based
diff --git a/doc/guide/files/makefile.xml b/doc/guide/files/makefile.xml
index 36f6bd6e90d..1b1e63d7045 100644
--- a/doc/guide/files/makefile.xml
+++ b/doc/guide/files/makefile.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: makefile.xml,v 1.15 2005/05/16 09:27:48 rillig Exp $ -->
+<!-- $NetBSD: makefile.xml,v 1.16 2005/05/24 12:14:42 wiz Exp $ -->
 
 <!-- based on:
 pkgsrc/bootstrap/bmake/for.c 1.1.1.1
@@ -128,7 +128,7 @@ pkgsrc/bootstrap/bmake/var.c 1.2
     use in your own code. If you don't find anything appropriate here,
     you should test your code and add it here.</para>
 
-    <sect2>
+    <sect2 id="adding-to-list">
       <title>Adding things to a list</title>
 
       <programlisting>
@@ -152,7 +152,7 @@ EXT_LIST+=              ${ANOTHER_EXT_LIST}     # 4
 
     </sect2>
 
-    <sect2>
+    <sect2 id="converting-internal-to-external">
       <title>Converting an internal list into an external list</title>
 
       <programlisting>
@@ -170,7 +170,7 @@ EXT_LIST+=      ${i:Q}""
 
     </sect2>
 
-    <sect2>
+    <sect2 id="passing-variable-to-shell">
       <title>Passing variables to a shell command</title>
 
       <programlisting>
@@ -216,7 +216,7 @@ all:
 
     </sect2>
 
-    <sect2>
+    <sect2 id="quoting-guideline">
       <title>Quoting guideline</title>
 
       <para>There are many possible sources of wrongly quoted variables.
@@ -305,7 +305,7 @@ for_test:
       </itemizedlist>
     </sect2>
 
-    <sect2>
+    <sect2 id="bsd-make-bug-workaround">
       <title>Workaround for a bug in BSD Make</title>
 
       <para>The pkgsrc bmake program does not handle the following
diff --git a/doc/guide/files/options.xml b/doc/guide/files/options.xml
index 1d860feea74..88ebab70398 100644
--- a/doc/guide/files/options.xml
+++ b/doc/guide/files/options.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: options.xml,v 1.4 2005/05/20 10:02:03 rillig Exp $ -->
+<!-- $NetBSD: options.xml,v 1.5 2005/05/24 12:14:42 wiz Exp $ -->
 
 <!-- based on:
 pkgsrc/mk/bsd.options.mk 1.23
@@ -15,7 +15,7 @@ pkgsrc/mk/bsd.options.mk 1.23
     of options will be built into a package or to allow a set of
     global default options apply. </para>
 
-    <sect1>
+    <sect1 id="global-default-options">
       <title>Global default options</title>
 
       <para> Global default options are listed in
@@ -25,7 +25,7 @@ pkgsrc/mk/bsd.options.mk 1.23
         <filename>/etc/mk.conf</filename>. </para>
     </sect1>
 
-    <sect1>
+    <sect1 id="converting-to-options">
       <title>Converting packages to use <filename>bsd.options.mk</filename></title>
 
       <para> The following example shows how
diff --git a/doc/guide/files/platforms.xml b/doc/guide/files/platforms.xml
index 5aeee09cf28..21bb8dc2e9e 100644
--- a/doc/guide/files/platforms.xml
+++ b/doc/guide/files/platforms.xml
@@ -1,9 +1,9 @@
-<!-- $NetBSD: platforms.xml,v 1.10 2005/05/15 20:33:01 rillig Exp $ -->
+<!-- $NetBSD: platforms.xml,v 1.11 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="platforms">
   <title>Using pkgsrc on systems other than &os;</title>
 
-  <sect1>
+  <sect1 id="bootstrapping-pkgsrc">
     <title>Bootstrapping pkgsrc</title>
 
     <para>For operating systems other than &os;, we provide a bootstrap kit to
@@ -74,12 +74,12 @@
       found on <ulink url="http://www.pkgsrc.org/">www.pkgsrc.org</ulink>.</para>
   </sect1>
 
-  <sect1>
+  <sect1 id="platform-specific-notes">
     <title>Platform specific notes</title>
 
     <para>Here are some platform-specific notes you should be aware of.</para>
 
-    <sect2>
+    <sect2 id="darwin">
       <title>Darwin (Mac OS X)</title>
 
       <para>Darwin 5.x and 6.x are supported. There are two methods of using
@@ -159,7 +159,7 @@
       </sect3>
     </sect2>
 
-    <sect2>
+    <sect2 id="freebsd">
       <title>FreeBSD</title>
 
       <para>
@@ -197,7 +197,7 @@
       </orderedlist>
     </sect2>
 
-    <sect2>
+    <sect2 id="interix">
       <title>Interix</title>
 
       <para>Interix is a POSIX compatible subsystem for the Windows NT kernel,
@@ -295,7 +295,7 @@
       </sect3>
     </sect2>
 
-    <sect2>
+    <sect2 id="irix">
       <title>IRIX</title>
 
       <para>You will need a working C compiler, either gcc or SGI's MIPS and MIPSpro
@@ -343,7 +343,7 @@
         '--preserve-path' flag.</para>
     </sect2>
 
-    <sect2>
+    <sect2 id="linux">
       <title>Linux</title>
 
       <para>
@@ -396,7 +396,7 @@
 
     </sect2>
 
-    <sect2>
+    <sect2 id="openbsd">
       <title>OpenBSD</title>
 
       <para>OpenBSD 3.0 and 3.2 are tested and supported.</para>
@@ -441,7 +441,7 @@
       </orderedlist>
     </sect2>
 
-    <sect2>
+    <sect2 id="solaris">
       <title>Solaris</title>
 
       <para>Solaris 2.6 through 9 are supported on both x86 and sparc. You will need a working C 
@@ -475,7 +475,7 @@
       <para>Please note the use of GNU binutils on Solaris is
 	<emphasis>not</emphasis> supported.</para>
 
-      <sect3>
+      <sect3 id="solaris-gcc-note">
 	<title>If you are using gcc</title>
 
 	<para>It makes life much simpler if you only use the same gcc consistently
@@ -489,7 +489,7 @@
 	    url="http://www.sun.com/bigadmin/common/freewareSearch.html">http://www.sun.com/bigadmin/common/freewareSearch.html</ulink>.</para>
       </sect3>
 
-      <sect3>
+      <sect3 id="solaris-sun-workshop-note">
 	<title>If you are using Sun WorkShop</title>
 
 	<para>You will need at least the following packages installed (from WorkShop
diff --git a/doc/guide/files/plist.xml b/doc/guide/files/plist.xml
index 74ab556097a..8416312b7dc 100644
--- a/doc/guide/files/plist.xml
+++ b/doc/guide/files/plist.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: plist.xml,v 1.4 2005/05/08 13:53:06 wiz Exp $ -->
+<!-- $NetBSD: plist.xml,v 1.5 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="plist">
   <title>PLIST issues</title>
@@ -13,7 +13,7 @@
     below!).</para>
 
 
-  <sect1>
+  <sect1 id="rcs-id">
     <title>RCS ID</title>
 
     <para>
@@ -24,7 +24,7 @@
     <programlisting>@comment &#36;NetBSD&#36;</programlisting>
   </sect1>
     
-  <sect1>
+  <sect1 id="automatic-plist-generation">
     <title>Semi-automatic <filename>PLIST</filename> generation</title>
 	    
     <para>You can use the <command>make print-PLIST</command> command
@@ -162,7 +162,7 @@
       in the PLIST with <quote>somevalue</quote>.  </para>
   </sect1>
 
-  <sect1>
+  <sect1 id="manpage-compression">
     <title>Manpage-compression</title>
     
     <para>Manpages should be installed in compressed form if
@@ -177,7 +177,7 @@
   </sect1>
 
   
-  <sect1>
+  <sect1 id="using-PLIST_SRC">
     <title>Changing PLIST source with <varname>PLIST_SRC</varname></title>
 
     <para>To use one or more files as source for the <filename>PLIST</filename> used
@@ -188,7 +188,7 @@
   </sect1>
 
 
-  <sect1>
+  <sect1 id="platform-specific-plist">
     <title>Platform specific and differing PLISTs</title>
     
     <para>Some packages decide to install a different set of files based on
diff --git a/doc/guide/files/submit.xml b/doc/guide/files/submit.xml
index 6faea4fb626..fd8788d411c 100644
--- a/doc/guide/files/submit.xml
+++ b/doc/guide/files/submit.xml
@@ -1,9 +1,9 @@
-<!-- $NetBSD: submit.xml,v 1.5 2005/05/08 13:53:06 wiz Exp $ -->
+<!-- $NetBSD: submit.xml,v 1.6 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="submit"> <?dbhtml filename="submit.html"?>
 <title>Submitting and Committing</title>
 
-<sect1>
+<sect1 id="submitting-your-package">
 <title>Submitting your packages</title>
 <para>
 You have to separate between binary and <quote>normal</quote> (source)
@@ -51,7 +51,7 @@ packages here:
 
 </sect1>
 
-<sect1>
+<sect1 id="committing-importing">
 <title>Committing: Importing a package into CVS</title>
 <para>
   This section is only of interest for pkgsrc developers with write
@@ -99,7 +99,7 @@ packages here:
 </para>
 </sect1>
 
-<sect1>
+<sect1 id="updating-package">
 <title>Updating a package to a newer version</title>
 <para>
   Please always put a concise, appropriate and relevant summary of the
@@ -143,7 +143,7 @@ packages here:
 </para>
 </sect1>
 
-<sect1>
+<sect1 id="moving-package">
 <title>Moving a package in pkgsrc</title>
 
 <orderedlist>
diff --git a/doc/guide/files/using.xml b/doc/guide/files/using.xml
index 7453bd41667..8a06bda66b5 100644
--- a/doc/guide/files/using.xml
+++ b/doc/guide/files/using.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: using.xml,v 1.9 2005/05/15 20:38:40 rillig Exp $ -->
+<!-- $NetBSD: using.xml,v 1.10 2005/05/24 12:14:42 wiz Exp $ -->
 
 <chapter id="using"> <?dbhtml filename="using.html"?>
   <title>Using pkgsrc</title>
@@ -10,7 +10,7 @@
       precompiled binary package that someone else already prepared
       for your type of machine. </para>
 
-    <sect2>
+    <sect2 id="where-to-get-binary-packages">
       <title>Where to get binary packages</title>
       
       <para> Precompiled packages are stored on ftp.NetBSD.org and its
@@ -34,7 +34,7 @@
         documentation for the exact location. </para>  
     </sect2>
 
-    <sect2>
+    <sect2 id="how-to-use-binary-packages">
       <title>How to use binary packages</title>
       
       <para> If you have the files on a CDROM or downloaded them to
@@ -79,7 +79,7 @@
         installed program. </para> 
     </sect2>
 
-    <sect2>
+    <sect2 id="a-word-of-warning">
       <title>A word of warning</title>
     
       <para> Please pay very careful attention to the warnings
@@ -91,14 +91,14 @@
     </sect2>
   </sect1>
 
-  <sect1>
+  <sect1 id="building-packages-from-source">
     <title>Building packages from source</title>
     
     <para> This assumes that the package is already in pkgsrc. If it
       is not, see <xref linkend="developers-guide"/> for instructions
       how to create your own packages.</para>
 
-    <sect2>
+    <sect2 id="requirements">
       <title>Requirements</title>
 
       <para> To build packages from source on a NetBSD system the
@@ -110,7 +110,7 @@
     </sect2>
     
 
-    <sect2>
+    <sect2 id="fetching-distfiles">
       <title>Fetching distfiles</title>
 
       <para>The first step for building a package is downloading the
@@ -136,7 +136,7 @@
         <filename>/usr/pkgsrc/distfiles</filename>.</para>
     </sect2>
 
-    <sect2>
+    <sect2 id="how-to-build-and-install">
       <title>How to build and install</title>
 
       <para>Assuming that the distfile has been fetched (see previous section), become
@@ -236,7 +236,7 @@
         install any if you use a non-standard <varname>LOCALBASE</varname>.</para>
     </sect2>
     
-    <sect2>
+    <sect2 id="selecting-the-compiler">
       <title>Selecting the compiler</title>
 
       <para>By default, pkgsrc will use GCC to build packages.  This may be