Wed Feb 11 05:05:20 2009 UTC ()
add missing xml-tag


(kano)
diff -r1.57 -r1.58 pkgsrc/doc/guide/files/build.xml
cvs diff -r1.57 -r1.58 pkgsrc/doc/guide/files/build.xml (expand / switch to unified diff)

--- pkgsrc/doc/guide/files/build.xml 2009/02/10 19:24:37 1.57
+++ pkgsrc/doc/guide/files/build.xml 2009/02/11 05:05:20 1.58
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: build.xml,v 1.57 2009/02/10 19:24:37 joerg Exp $ --> 1<!-- $NetBSD: build.xml,v 1.58 2009/02/11 05:05:20 kano Exp $ -->
2 2
3<chapter id="build"> 3<chapter id="build">
4 <title>The build process</title> 4 <title>The build process</title>
5 5
6 <sect1 id="build.intro"> 6 <sect1 id="build.intro">
7 <title>Introduction</title> 7 <title>Introduction</title>
8 8
9 <para>This chapter gives a detailed description on how a package is 9 <para>This chapter gives a detailed description on how a package is
10 built. Building a package is separated into different 10 built. Building a package is separated into different
11 <emphasis>phases</emphasis> (for example <varname>fetch</varname>, 11 <emphasis>phases</emphasis> (for example <varname>fetch</varname>,
12 <varname>build</varname>, <varname>install</varname>), all of which are 12 <varname>build</varname>, <varname>install</varname>), all of which are
13 described in the following sections. Each phase is splitted into 13 described in the following sections. Each phase is splitted into
14 so-called <emphasis>stages</emphasis>, which take the name of the 14 so-called <emphasis>stages</emphasis>, which take the name of the
@@ -374,27 +374,27 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site @@ -374,27 +374,27 @@ ${FETCH_CMD} ${FETCH_BEFORE_ARGS} ${site
374 <varname>MASTER_SITE_OVERRIDE</varname> is tried, then the 374 <varname>MASTER_SITE_OVERRIDE</varname> is tried, then the
375 sites specified in either <varname>SITES.file</varname> if 375 sites specified in either <varname>SITES.file</varname> if
376 defined, else <varname>MASTER_SITES</varname> or 376 defined, else <varname>MASTER_SITES</varname> or
377 <varname>PATCH_SITES</varname>, as applies, then finally the 377 <varname>PATCH_SITES</varname>, as applies, then finally the
378 value of <varname>MASTER_SITE_BACKUP</varname>. The order of 378 value of <varname>MASTER_SITE_BACKUP</varname>. The order of
379 all except the first and the last can be optionally sorted 379 all except the first and the last can be optionally sorted
380 by the user, via setting either 380 by the user, via setting either
381 <varname>MASTER_SORT_RANDOM</varname>, and 381 <varname>MASTER_SORT_RANDOM</varname>, and
382 <varname>MASTER_SORT_AWK</varname> or 382 <varname>MASTER_SORT_AWK</varname> or
383 <varname>MASTER_SORT_REGEX</varname>.</para> 383 <varname>MASTER_SORT_REGEX</varname>.</para>
384 384
385 <para> The specific command and arguments used depend on the 385 <para> The specific command and arguments used depend on the
386 <varname>FETCH_USING</varname> parameter. The example above is 386 <varname>FETCH_USING</varname> parameter. The example above is
387 for <literal>FETCH_USING=custom</literal>. 387 for <literal>FETCH_USING=custom</literal>.</para>
388 388
389 <para>The distfiles mirror run by the NetBSD Foundation uses the 389 <para>The distfiles mirror run by the NetBSD Foundation uses the
390 <emphasis>mirror-distfiles</emphasis> target to mirror the 390 <emphasis>mirror-distfiles</emphasis> target to mirror the
391 distfiles, if they are freely distributable. Packages setting 391 distfiles, if they are freely distributable. Packages setting
392 <varname>NO_SRC_ON_FTP</varname> (usually to 392 <varname>NO_SRC_ON_FTP</varname> (usually to
393 <quote>${RESTRICTED}</quote>) will not have their distfiles 393 <quote>${RESTRICTED}</quote>) will not have their distfiles
394 mirrored.</para> 394 mirrored.</para>
395 </sect2> 395 </sect2>
396 396
397 </sect1> 397 </sect1>
398 398
399 <sect1 id="build.checksum"> 399 <sect1 id="build.checksum">
400 <title>The <emphasis>checksum</emphasis> phase</title> 400 <title>The <emphasis>checksum</emphasis> phase</title>