 @@ -1,14 +1,14 @@
-<!-- $NetBSD: build.xml,v 1.85 2020/06/20 15:25:01 rillig Exp $ -->
+<!-- $NetBSD: build.xml,v 1.86 2021/04/06 17:21:17 nia Exp $ -->
 <chapter id="build">
   <title>The build process</title>
   <sect1 id="build.intro">
     <title>Introduction</title>
     <para>This chapter gives a detailed description on how a package is
     built. Building a package is separated into different
     <emphasis>phases</emphasis> (for example <varname>fetch</varname>,
     <varname>build</varname>, <varname>install</varname>), all of which are
     described in the following sections. Each phase is split into
     so-called <emphasis>stages</emphasis>, which take the name of the
 @@ -1059,75 +1059,75 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
 	  PKG=<replaceable>somepackage</replaceable></command>.</para>
 	  <para>Running this command takes a very long time, some
 	  hours even on fast machines!</para>
 	</listitem>
       </varlistentry>
       <varlistentry>
 	<term>readme</term>
 	<listitem>
 	  <para>This target generates a
-	  <filename>README.html</filename> file, which can be
+	  <filename>index.html</filename> file, which can be
 	  viewed using a browser such as <filename
 	  role="pkg">www/firefox</filename> or <filename
 	  role="pkg">www/links</filename>.  The generated files
 	  contain references to any packages which are in the
 	  <varname>PACKAGES</varname> directory on the local
 	  host. The generated files can be made to refer to URLs
 	  based on <varname>FTP_PKG_URL_HOST</varname> and
 	  <varname>FTP_PKG_URL_DIR</varname>. For example, if I
-	  wanted to generate <filename>README.html</filename>
+	  wanted to generate <filename>index.html</filename>
 	  files which pointed to binary packages on the local
 	  machine, in the directory
 	  <filename>/usr/packages</filename>, set
 	  <varname>FTP_PKG_URL_HOST=file://localhost</varname> and
 	  <varname>FTP_PKG_URL_DIR=/usr/packages</varname>. The
 	  <varname>${PACKAGES}</varname> directory and its
 	  subdirectories will be searched for all the binary
 	  packages.</para>
 	  <para>The target can be run at the toplevel or in category
 	  directories, in which case it descends recursively.</para>
 	</listitem>
       </varlistentry>
       <varlistentry>
 	<term>readme-all</term>
 	<listitem>
 	  <para>This is a top-level command, run it in
 	  <filename>pkgsrc</filename>.  Use this target to create a
 	  file <filename>README-all.html</filename> which contains a
 	  list of all packages currently available in the &os;
 	  Packages Collection, together with the category they belong
 	  to and a short description. This file is compiled from the
-	  <filename>pkgsrc/*/README.html</filename> files, so be sure
+	  <filename>pkgsrc/*/index.html</filename> files, so be sure
 	  to run this <emphasis>after</emphasis> a <command>make
 	  readme</command>.</para>
 	</listitem>
       </varlistentry>
       <varlistentry>
 	<term>cdrom-readme</term>
 	<listitem>
 	  <para>This is very much the same as the
 	  <quote>readme</quote> target (see above), but is to be
 	  used when generating a pkgsrc tree to be written to a
 	  CD-ROM.  This target also produces
-	  <filename>README.html</filename> files, and can be made
+	  <filename>index.html</filename> files, and can be made
 	  to refer to URLs based on
 	  <varname>CDROM_PKG_URL_HOST</varname> and
 	  <varname>CDROM_PKG_URL_DIR</varname>.</para>
 	</listitem>
       </varlistentry>
       <varlistentry>
 	<term>show-distfiles</term>
 	<listitem>
 	  <para>This target shows which distfiles and patchfiles
 	  are needed to build the package
 	  (<varname>ALLFILES</varname>, which contains all