
ALFS DTD

Version 3.1-2004-02-23

ALFS DTD Development Team

   Copyright  2001-2004 ALFS DTD Development Team

   This book explains in detail how to use ALFS DTD v3.1.

   Copyright (c) 2001-2004, ALFS DTD Development Team

   All rights reserved.

   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are
   met:
     * Redistributions in any form must retain the above copyright
       notice, this list of conditions and the following disclaimer.
     * Neither the name of "Linux From Scratch", "Automated Linux From
       Scratch" nor the names of its contributors may be used to endorse
       or promote products derived from this material without specific
       prior written permission.
     * Any material derived from Linux From Scratch must contain a
       reference to the "Linux From Scratch" project.
     * Any material derived from Automated Linux From Scratch must
       contain a reference to the "Automated Linux From Scratch" project.

   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
   ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
   A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
   CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
   EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
   PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
   LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
   NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
     _________________________________________________________________
     _________________________________________________________________

Dedication

   This book is dedicated to the LFS and ALFS communities.

   Table of Contents
   [1]Preface

        [2]ChangeLog
        [3]Who Would Want To Read This Book
        [4]Contact Information

              [5]Mailing Lists
              [6]News Server
              [7]WWW Links
              [8]Other

        [9]Acknowledgements
        [10]Conventions Used In This Book

   1. [11]Description of the ALFS Profile Syntax

        [12]ALFS DTD Introduction
        [13]Element : <alfs>

              [14]Syntax
              [15]Description
              [16]Examples

        [17]Element : <archive>

              [18]Syntax
              [19]Description
              [20]Examples

        [21]Element : <base>

              [22]Syntax
              [23]Description
              [24]Examples

        [25]Element : <configure>

              [26]Syntax
              [27]Description
              [28]Examples

        [29]Element : <content>

              [30]Syntax
              [31]Description
              [32]Examples

        [33]Element : <copy>

              [34]Syntax
              [35]Description
              [36]Examples

        [37]Element : <description>

              [38]Syntax
              [39]Description
              [40]Examples

        [41]Element: <destination>

              [42]Syntax
              [43]Description
              [44]Examples

        [45]Element: <digest>

              [46]Syntax
              [47]Description
              [48]Examples

        [49]Element: <download>

              [50]Syntax
              [51]Description
              [52]Examples

        [53]Element: <environment>

              [54]Syntax
              [55]Description
              [56]Examples

        [57]Element: <execute>

              [58]Syntax
              [59]Description
              [60]Examples

        [61]Element: <file>

              [62]Syntax
              [63]Description
              [64]Examples

        [65]Element: <find>

              [66]Syntax
              [67]Description
              [68]Examples

        [69]Element: <item>

              [70]Syntax
              [71]Description
              [72]Examples

        [73]Element: <link>

              [74]Syntax
              [75]Description
              [76]Examples

        [77]Element: <list>

              [78]Syntax
              [79]Description
              [80]Examples

        [81]Element: <make>

              [82]Syntax
              [83]Description
              [84]Examples

        [85]Element: <mkdir>

              [86]Syntax
              [87]Description
              [88]Examples

        [89]Element: <move>

              [90]Syntax
              [91]Description
              [92]Examples

        [93]Element: <name>

              [94]Syntax
              [95]Description
              [96]Examples

        [97]Element: <option>

              [98]Syntax
              [99]Description
              [100]Examples

        [101]Element: <ownership>

              [102]Syntax
              [103]Description
              [104]Examples

        [105]Element: <package>

              [106]Syntax
              [107]Description
              [108]Examples

        [109]Element: <packageinfo>

              [110]Syntax
              [111]Description
              [112]Examples

        [113]Element: <para>

              [114]Syntax
              [115]Description
              [116]Examples

        [117]Element: <param>

              [118]Syntax
              [119]Description
              [120]Examples

        [121]Element: <patch>

              [122]Syntax
              [123]Description
              [124]Examples

        [125]Element: <permissions>

              [126]Syntax
              [127]Description
              [128]Examples

        [129]Element: <prefix>

              [130]Syntax
              [131]Description
              [132]Examples

        [133]Element: <reference>

              [134]Syntax
              [135]Description
              [136]Examples

        [137]Element: <remove>

              [138]Syntax
              [139]Description
              [140]Examples

        [141]Element: <replace>

              [142]Syntax
              [143]Description
              [144]Examples

        [145]Element: <requires>

              [146]Syntax
              [147]Description
              [148]Examples

        [149]Element: <root>

              [150]Syntax
              [151]Description
              [152]Examples

        [153]Element: <search_replace>

              [154]Syntax
              [155]Description
              [156]Examples

        [157]Element: <source>

              [158]Syntax
              [159]Description
              [160]Examples

        [161]Element: <stage>

              [162]Syntax
              [163]Description
              [164]Examples

        [165]Element: <stageinfo>

              [166]Syntax
              [167]Description
              [168]Examples

        [169]Element: <target>

              [170]Syntax
              [171]Description
              [172]Examples

        [173]Element: <textdump>

              [174]Syntax
              [175]Description
              [176]Examples

        [177]Element: <unpack>

              [178]Syntax
              [179]Description
              [180]Examples

        [181]Element: <url>

              [182]Syntax
              [183]Description
              [184]Examples

        [185]Element: <user>

              [186]Syntax
              [187]Description
              [188]Examples

        [189]Element: <utilizes>

              [190]Syntax
              [191]Description
              [192]Examples

        [193]Element: <variable>

              [194]Syntax
              [195]Description
              [196]Examples

        [197]Element: <version>

              [198]Syntax
              [199]Description
              [200]Examples
     _________________________________________________________________

Preface

ChangeLog

   3.1-2004-02-23 - February 23, 2004
     * February 23rd, 2004 [jwrober]: Finished the download element
       description. Closes bug 760.
     * February 23rd, 2004 [jwrober]: Finished the url element
       description. Closes bug 769.
     * February 23rd, 2004 [jwrober]: Finished the digest element
       description. Closes bug 759.
     * February 23rd, 2004 [jwrober]: Fixed copy element description.
       Closes bug 758.
     * February 23rd, 2004 [jwrober]: Fixed wierd character in
       acknowledgements page. Closes bug 755.
     * February 22nd, 2004 [jwrober]: Finished a first pass over the rest
       of the elements.
     * November 5th, 2003 [jwrober]: Added elem_prefix.
     * November 5th, 2003 [jwrober]: Updated elem_configure, elem_copy,
       elem_description to match the DTD and standardized to the rest of
       the doc.
     * November 4th, 2003 [jwrober]: Updated elem_alfs, elem_archive,
       elem_base to match the DTD; also began the element standardization
       with the elem_alfs element's page.
     * November 3rd, 2003 [jwrober]: Standardized headings.
     * November 3rd, 2003 [jwrober]: Updated acknowledgements,
       conventions and general preface pages.
     * September 30th, 2003 [jwrober]: Added an alfs_dtd intro page.
     * September 26th, 2003 [jwrober]: Modified the header of each page
       to conform with the DocBook rules that the LFS and BLFS books use
       (for consistency).
     * September 24th, 2003 [jwrober]: Removed all references to nALFS,
       moved files to the ALFS/docs from the ALFS/nALFS/doc moudule in
       CVS.
     * September 22nd, 2003 [jwrober]: Various changes to file locations
       and began standardizing document look and feel like the LFS and
       BLFS Books.
     * September 18th, 2003 [vdzuba]: Reorganized the document, now split
       into small chunks.
     * February 20th, 2003 [vdzuba]: Added the elements <if>, <then> and
       <else>.
     * February 5th, 2003 [vdzuba]: Added an option to <link> and added
       element <version>.
     * January 19th, 2003 [vdzuba]: Upgraded to version 3.1 of the DTD.
     * January 8th, 2003 [vdzuba]: Replaced "option?" by "option*" in
       copy.
     * December 5th, 2002 [vdzuba]: Added bash script equivalent to all
       examples.
     * October 22nd, 2002 [vdzuba]: Replaced "parent" with "parents" in
       mkdir.
     * October 21st, 2002 [vdzuba]: Added element <digest>.
     * October 13th, 2002 [vdzuba]: Make attribute append of <variable>
       optional.
     * September 5th, 2002 [vdzuba]: Added chapter with syntax.
     * May 7th, 2002 [highos]: Initial structure.
     _________________________________________________________________

Who Would Want To Read This Book

   This book is mainly aimed at those who want more information on the
   ALFS DTD. The DTD is designed to be implementation agnostic. This
   means that you may be reading this book as part of an ALFS
   implementation source tarball or on the ALFS website.
     _________________________________________________________________

Contact Information

Mailing Lists

   The ALFS DTD uses two mailing list hosted from the Linux From Scratch
   servers.

   Please direct the majority of your emails to the ALFS mailing list at
   [201]alfs-discuss@linuxfromscratch.org. This is an excellent place to
   post questions and bug reports. For complete mailing list information,
   refer to
   [202]http://www.linuxfromscratch.org/mailman/listinfo/alfs-discuss.

   The second list is really for the development team's use and is
   available at [203]alfs-log@linuxfromscratch.org. This is an excellent
   place to see the daily activity of the project. For complete mailing
   list information, refer to
   [204]http://www.linuxfromscratch.org/mailman/listinfo/alfs-log
     _________________________________________________________________

News Server

   All the mailing lists hosted at linuxfromscratch.org are also
   accessible via the NNTP server. All messages posted to a mailing list
   will be copied to its correspondent newsgroup, and vice versa.

   The news server can be reached at [205]news.linuxfromscratch.org.
     _________________________________________________________________

WWW Links

   Some other xrefs that might interest you:

   Linux From Scratch:

     [206]http://www.linuxfromscratch.org

   Automated Linux From Scratch:

     [207]http://www.linuxfromscratch.org/alfs
     _________________________________________________________________

Other

   The current ALFS DTD documentation maintainer is James Robertson. If
   you need to reach James, send an email to
   [208]jwrober@linuxfromscratch.org.
     _________________________________________________________________

Acknowledgements

   We would like to thank the following people and organizations for
   their contributions towards the Automated Linux From Scratch project:
     * [209]Vassili Dzuba <vassili@linuxfromscratch.org> -- for helping
       to create the DTD and writing the intial version of this book.
     * [210]Gerard Beekmans <gerard@linuxfromscratch.org> -- for being
       more then a great help.
     * [211]James Robertson <jwrober@linuxfromscratch.org> -- Current
       documentation editor.
     * Jesse Tien-Ten-Que for helping to create the DTD and writing the
       initial version of this book.
     * Countless other people on the ALFS mailing list who are making
       this project happen by giving their suggestions, testing the tools
       and submitting bug reports.
     _________________________________________________________________

Conventions Used In This Book

   To make things easy to follow, there are a number of conventions used
   throughout the book. Following are some examples:
   ./configure --prefix=/usr

     This form of text is designed to be typed in exactly as seen unless
     otherwise noted in the surrounding text.

   install-info: unknown option '--dir-file=/mnt/lfs/usr/info/dir'

     This form of text (fixed width text) is showing screen output,
     probably as the result of commands issued and is also used to show
     filenames such as /bin/grep

   Emphasis

     This form of text is used for several purposes in the book but
     mainly to emphasize important points or to give examples as to what
     to type.

   [212]http://www.linuxfromscratch.org/alfs

     This form of text is used for hyperxrefs, both within the book and
     to external pages such as HowTo's, download locations, websites,
     etc.

cat > $LFS/etc/group << "EOF">
        root:x:0:
        bin:x:1:
        ......
EOF

     This type of section is used mainly when creating configuration
     files. The first command (in bold) tells the system to create the
     file $LFS/etc/group from whatever is typed on the following lines
     until the sequence EOF is encountered. Therefore, this whole
     section is generally typed as seen.
     _________________________________________________________________

Chapter 1. Description of the ALFS Profile Syntax

ALFS DTD Introduction

   ALFS profiles are written using an XML syntax. This chapter describes
   the various XML elements that can occur in a profile.

   For each element, the book describes:
     * the formal definition of the element, using the exact DTD syntax
     * a description of the element
     * one or several examples
     * an equivalent bash script(s) for the examples (when applicable)
     _________________________________________________________________

Element : <alfs>

Syntax


<!ELEMENT alfs           ((configure | copy | download | execute | link |
                           make | mkdir | move | ownership | package |
                           patch | permissions | remove | search_replace |
                           stage | textdump | unpack)*)>
<!ATTLIST alfs
          base           CDATA #IMPLIED
          version        CDATA #FIXED "3.1">

   See also : [213]Element : <configure> | [214]Element : <copy> |
   [215]Element: <download> | [216]Element: <execute> | [217]Element:
   <link> | [218]Element: <make> | [219]Element: <mkdir> | [220]Element:
   <move> | [221]Element: <ownership> | [222]Element: <package> |
   [223]Element: <patch> | [224]Element: <permissions> | [225]Element:
   <remove> | [226]Element: <search_replace> | [227]Element: <stage> |
   [228]Element: <textdump> | [229]Element: <unpack>
     _________________________________________________________________

Description

   The element alfs is the root element of the ALFS DTD. This means that
   an ALFS profile should contain one and only one alfs element with all
   the other elements being embedded within this element.

   When processing an alfs element, one processes all its embedded
   children in their order of occurence.

   Notice that all the main operation elements (configure to unpack) are
   surrounded by parathensis [ ( ) ] and followed by an asterisk [ * ].
   The asterisk signifies that each main operation element can be used
   optionally inside the alfs declaration in a profile and that, if used,
   they can be used more than once.

   The attribute base is used to specify the base directory which will be
   used by all the commands in the element alfs. The use of #IMPLIED
   denotes that this attribute is optional. If not used, base will
   inherit its value from an earlier use in the profile. See [230]Element
   : <base>.

   The attribute version identifies the version of the ALFS profile
   syntax used; it should be "3.1".
     _________________________________________________________________

Examples

<!DOCTYPE alfs SYSTEM "alfs-3.1.dtd" [

        <!ENTITY % general_entities SYSTEM "entities/general">

        %general_entities;

]>

<alfs version="3.1">

 .....

</alfs>

   There is no equivalent Bash script example for this element.
     _________________________________________________________________

Element : <archive>

Syntax


<!ELEMENT archive        (#PCDATA)>

   This element occurs in the element : [231]Element: <unpack>.
     _________________________________________________________________

Description

   The element archive is used to specify the archive file in an unpack
   operation.
     _________________________________________________________________

Examples

<unpack>
        <archive>/usr/src/lfs-packages/gzip.1.2.4a.tar.gz</archive>
        <destination>/usr/src</destination>
</unpack>

   The equivalent bash script is :
echo Unpacking /usr/src/lfs-packages/gzip.1.2.4a.tar.gz into /usr/src
cd /usr/src
tar -xzvf /usr/src/lfs-packages/gzip.1.2.4a.tar.gz
     _________________________________________________________________

Element : <base>

Syntax


<!ELEMENT base           (#PCDATA)>

   This element occurs in the element : [232]Element: <stageinfo>
     _________________________________________________________________

Description

   The element base is used to specify the base directory which will be
   used by all the commands in the stage (inherited), unless another base
   is specified at the level of the command as an attribute. See also :
   [233]Element : <alfs> | [234]Element : <configure> | [235]Element :
   <copy> | [236]Element: <execute> | [237]Element: <link> |
   [238]Element: <make> | [239]Element: <mkdir> | [240]Element: <move> |
   [241]Element: <ownership> | [242]Element: <patch> | [243]Element:
   <permissions> | [244]Element: <search_replace> | [245]Element:
   <textdump>
     _________________________________________________________________

Examples

<stage>
        <stageinfo>
                <base>/usr/src/gzip.1.2.4a</base>
        </stageinfo>

        <configure>
        </configure>

        <make>
        </make>

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Entering Stage
cd /usr/src/gzip.1.2.4a

echo Executing configure
./configure

echo Executing make
make

echo Executing make
make install

echo Exiting stage
     _________________________________________________________________

Element : <configure>

Syntax


<!ELEMENT configure      ((param | prefix)*)>
<!ATTLIST configure
          base           CDATA #IMPLIED
          command        CDATA #IMPLIED>

   This element is an element of : [246]Element : <alfs> | [247]Element:
   <stage>

   See also : [248]Element: <param> | [249]Element: <prefix>
     _________________________________________________________________

Description

   The element configure is one of the many main operation elements. The
   element configure is used to describe the command configure.

   Notice that the elements param and prefix are surrounded by
   parathensis [ ( ) ] and followed by an asterisk [ * ]. The asterisk
   signifies that each element can be used optionally inside the
   configure declaration in a profile and that, if used, they can be used
   more than once.

   When processing the element, one executes the command ./configure with
   the parameter(s) and prefix(es) specified.

   The attribute base allows you to specify the directory in which the
   command is executed. See [250]Element : <base>.

   The attribute command allows you to specify a custom command if you
   don't want to use the default ./configure. This is extremely useful
   when running ./configure in a build directory outside the main source
   directory. The packages gcc and glibc often require this.
     _________________________________________________________________

Examples

   This example calls configure without any parameters :
<configure base="/usr/src/mypackage/">
</configure>

   The equivalent bash script is :
echo Executing configure
cd /usr/src/mypackage/
./configure

   This example calls configure with a parameter :
<configure base="/usr/src/mypackage/">
        <prefix>CFLAGS="..."<prefix>
        <prefix>CXXFLAGS="..."<prefix>
        <param>--prefix=/opt/mypackage</param>
</configure>

   The equivalent bash script is :
echo Executing configure
cd /usr/src/mypackage/
./configure --prefix=/opt/mypackage

   This example calls configure with a parameter and an explicit command
   :
<configure base="/usr/src/mypackage/" command="PATH=/usr/local/bin ./configure"
>
        <param>--prefix=/opt/mypackage</param>
</configure>

   The equivalent bash script is :
echo Executing configure
cd /usr/src/mypackage/
PATH=/usr/local/bin ./configure --prefix=/opt/mypackage
     _________________________________________________________________

Element : <content>

Syntax


<!ELEMENT content        (#PCDATA)>

   This element occurs in the element : [251]Element: <textdump>.
     _________________________________________________________________

Description

   The element content is used to specify the content of the file being
   created when processing a textdump operation.

     Note: Of course, it is possible to use XML entity references in the
     #PCDATA or string of this element.
     _________________________________________________________________

Examples

<textdump base="/etc">
        <file>group</file>

        <content>
                =root:x:0:
                =bin:x:1:
                =sys:x:2:
                =kmem:x:3:
                =tty:x:4:
                =tape:x:5:
                =daemon:x:6:
                =floppy:x:7:
                =disk:x:8:
                =lp:x:9:
                =dialout:x:10:
                =audio:x:11:
        </content>
</textdump>

   The equivalent bash script is :
echo Generating file group
cd /etc
cat > group << 'EOF'
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:4:
tape:x:5:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
EOF
     _________________________________________________________________

Element : <copy>

Syntax


<!ELEMENT copy           (option*, source+, destination)>
<!ATTLIST copy
          base           CDATA #IMPLIED>

   This element is an element of : [252]Element : <alfs> | [253]Element:
   <stage>

   See also : [254]Element: <option> | [255]Element: <source> |
   [256]Element: <destination>
     _________________________________________________________________

Description

   The element copy is one of the many main operation elements. It is
   used to copy a file and/or directory into a destination file or
   directory. The use of wildcards is not supported.

   The element option is optional and can be used one or many times to
   ensure the correct use of the cp command. The following is the
   currently supported list of options for the cp command :
     * archive (-a, --archive)
     * force (-f, --force)
     * no-dereference (-d, --no-dereference)
     * preserve (-p, --preserve)
     * recursive (-R, -r, --recursive)

   .

   The element source is required and can be used many times to provide
   multiple source locations for a file.

   The element destination is required and can only be used once. A copy
   can only have one destination.

   The attribute base allows you to specify the directory in which the
   command is executed. See [257]Element : <base>.
     _________________________________________________________________

Examples

<copy base="/usr/src/mypackage">
        <option>force</option>
        <source>config.txt</source>
        <destination>/opt/mypackage/config.txt</destination>
</copy>

   The equivalent bash script is :
echo Copying 'config.txt into /opt/mypackage/config.txt'
cd /usr/src/mypackage
cp -f config.txt /opt/mypackage/config.txt
     _________________________________________________________________

Element : <description>

Syntax


<!ELEMENT description    (para | list)*>

   This element occurs in the element : [258]Element: <packageinfo>

   See also : [259]Element: <para> | [260]Element: <list>
     _________________________________________________________________

Description

   The element description contains the description of a package. Its use
   is for documentation only.

   Notice that all the elements para and list are surrounded by
   parathensis [ ( ) ] and followed by an asterisk [ * ]. The asterisk
   signifies that each element can be used optionally inside the
   description declaration in a profile and that, if used, they can be
   used more than once.
     _________________________________________________________________

Examples

<package name="gimp" version="1.2.3">
        <packageinfo>
                <description>
                        <para>The gimp package contains the GNU Image Manipulat
ion Program. This is
                        useful for photo retouching, image composition and imag
e authoring.
                        </para>
                </description>

                <requires><name>gtk+</name></requires>

                        <utilizes><name>libtiff</name></utilizes>
                        <utilizes><name>libpng</name></utilizes>
                        <utilizes><name>libjpeg</name></utilizes>
                        <utilizes><name>aalib</name></utilizes>
                        <utilizes><name>mpeg_lib</name></utilizes>
                        <utilizes><name>python</name></utilizes>

                </required>

        ....

</package>

   There is no equivalent Bash script example for this element.
     _________________________________________________________________

Element: <destination>

Syntax


<!ELEMENT destination    (#PCDATA)>

   This element occurs in the elements : [261]Element : <copy> |
   [262]Element: <download> | [263]Element: <move> | [264]Element:
   <unpack> |
     _________________________________________________________________

Description

   The element destination is used to specify the name of the destination
   file or directory when processing a [265]Element : <copy> |
   [266]Element: <move> | [267]Element: <unpack> element.

   It is also used to specify the path of the destination directory when
   processing a [268]Element: <download> element.
     _________________________________________________________________

Examples

   The first example is an unpack command.
<unpack>
        <archive>/usr/src/lfs-packages/gzip.1.2.4a.tar.gz</archive>
        <destination>/usr/src</destination>
</unpack>

   The equivalent bash script is :
echo Unpacking /usr/src/lfs-packages/gzip.1.2.4a.tar.gz into /usr/src
cd /usr/src
tar -xzvf /usr/src/lfs-packages/gzip.1.2.4a.tar.gz

   The second example is a copy command.
<copy base="/usr/src/mypackage">
        <option>force</option>
        <source>config.txt</source>
        <destination>/opt/mypackage/config.txt</destination>
</copy>

   The equivalent bash script is :
echo Copying 'config.txt into /opt/mypackage/config.txt'
cd /usr/src/mypackage
cp -f  config.txt /opt/mypackage/config.txt
     _________________________________________________________________

Element: <digest>

Syntax


<!ELEMENT digest         (#PCDATA)>
<!ATTLIST digest
          type           CDATA "md5">

   This element occurs in the elements ; [269]Element: <download> |
   [270]Element: <unpack>
     _________________________________________________________________

Description

   The element digest is used to specify the MD5 digest hash of the
   archive file to be unpacked, or of the file to be downloaded.

   The attribute type is preset as an MD5 hash.
     _________________________________________________________________

Examples

<download>
        <file>kbd-1.08.tar.gz</file>
        <url>ftp://ftp.win.tue.nl/pub/linux-local/utils/kbd/</url>
        <destination>/tmp/</destination>
        <digest>924e6a05e52715dc0f96385b35f2f680</digest>
</download>

   There is no equivalent Bash script example for this element.
     _________________________________________________________________

Element: <download>

Syntax


<!ELEMENT download       (file, url*, destination, digest?)>

   This element occurs in the elements : [271]Element : <alfs> |
   [272]Element: <stage>

   See also : [273]Element: <file> | [274]Element: <url> | [275]Element:
   <destination> | [276]Element: <digest>
     _________________________________________________________________

Description

   The element download is one of the many main operation elements. It is
   used to specify one or several URLs from which a file can be
   downloaded, and optionally a digest to check that the file being
   downloaded if the right one.

   The sub-element file contains the name of the file to be downloaded.

   The sub-element url contains the url of the directory from which the
   download is performed. It should be terminated by a slash [ / ]. More
   precisely, the actual URL used for the download is the catenation of
   the content of the url element with the content of the file element.
   This element is optional, but if used can be used more than once.

   The sub-element destination contains the path of the directory into
   which the download should be performed.

   The sub-element digest contains the value with which the digest
   computed from the dowloaded file will be compared. This sub-element is
   optional. For more information see : [277]Element: <digest>

   If the file is already present in the destination directory, no
   download is performed but the digest is checked if present.
     _________________________________________________________________

Examples

<download>
        <file>kbd-1.08.tar.gz</file>
        <url>ftp://ftp.win.tue.nl/pub/linux-local/utils/kbd/</url>
        <destination>/tmp/</destination>
        <digest>924e6a05e52715dc0f96385b35f2f680</digest>
</download>

   There is no equivalent Bash script example for this element.
     _________________________________________________________________

Element: <environment>

Syntax


<!ELEMENT environment    (variable+)>
<!ATTLIST environment
          mode           ((append | prepend)?)>

   This element occurs in the element : [278]Element: <stageinfo>

   See also : [279]Element: <variable>
     _________________________________________________________________

Description

   The element environment allows you to define one or more environment
   variables to be added to the system environment used when calling the
   commands of the stage to which it applies.

   By default, the supplied value replaces any existing value for the
   specified variable. The attribute mode allows you to specify whether
   the supplied value should be prepended or appended to the existing
   value.
     _________________________________________________________________

Examples

<stage>
        <stageinfo>
                <base>/usr/src/gzip.1.2.4a</base>
        <environment>
                <variable name="GCCFLAGS">-O2</variable>
                <variable name="PATH" mode="prepend">/usr/src/gzip.1.2.4a:</var
iable>
                <variable name="LDFLAGS" mode="append"> -s</variable>
                </environment>
        </stageinfo>

        <configure />

        <make />

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Stage

export GCCFLAGS=-O2
export PATH=/usr/src/gzip.1.2.4a:$PATH
export LDFLAGS="$LDFLAGS -s"

echo Executing configure
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
cd /usr/src/gzip.1.2.4a
make

echo Executing make
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage
     _________________________________________________________________

Element: <execute>

Syntax


<!ELEMENT execute        ((param | prefix)*)>
<!ATTLIST execute
          base           CDATA #IMPLIED
          command        CDATA #REQUIRED>

   This element occurs in the elements : [280]Element : <alfs> |
   [281]Element: <stage>

   See also : [282]Element: <param> | [283]Element: <prefix>
     _________________________________________________________________

Description

   The element execute is one of the many main operation elements. It is
   used to execute an arbitrary command.

   The sub-element param contains one or many optional parameters of the
   command.

   The sub-element prefix contains any prefix data for the command to
   execute.

   Both sub-elements are optional, but if used can be used more than
   once.

   The attribute base allows you to specify the directory in which the
   command will be executed. See [284]Element : <base>.

   The attribute command contains the text of the command itself.
     _________________________________________________________________

Examples

   The first example is an execute command without a parameter.
   <execute command="umount">

   The equivalent bash script is :
echo Executing 'umount'
umount

   The second example is an execute command with one parameter.
<execute command="mount">
        <param>/mnfs/lfs</param>
</execute>

   The equivalent bash script is :
echo Executing 'mount'
mount /mnfs/lfs
     _________________________________________________________________

Element: <file>

Syntax


<!ELEMENT file           (#PCDATA)>

   This element occurs in the elements ; [285]Element: <download> |
   [286]Element: <search_replace> | [287]Element: <textdump>.
     _________________________________________________________________

Description

   The element file is used to specify the file in a download,
   search_replace or textdump operation.
     _________________________________________________________________

Examples

   The first example is a search_replace.
<search_replace base="/usr/src/mypackage">
        <file>runit.sh</file>
        <find>BINDIR</find>
        <replace>/bin</replace>
</search_replace>

   The equivalent bash script is :
echo Performing substitution in runit.sh
cd /usr/src/mypackage
cp runit.sh /tmp/foo.$$
sed -e 's/BINDIR/\/bin/' /tmp/foo.$$ > runit.sh

   The second example is a textdump.
<textdump base="/etc">
        <file>group</file>

        <content>
                =root:x:0:
                =bin:x:1:
                =sys:x:2:
                =kmem:x:3:
                =tty:x:4:
                =tape:x:5:
                =daemon:x:6:
                =floppy:x:7:
                =disk:x:8:
                =lp:x:9:
                =dialout:x:10:
                =audio:x:11:
        </content>
</textdump>

   The equivalent bash script is :
echo Generating file group
cd /etc

cat > group << 'EOF'
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:4:
tape:x:5:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
EOF
     _________________________________________________________________

Element: <find>

Syntax


<!ELEMENT find           (#PCDATA)>

   This element occurs in the element : [288]Element: <search_replace>
     _________________________________________________________________

Description

   The element find allows you to specify the string to be searched in a
   search and replace operation.
     _________________________________________________________________

Examples

<search_replace base="/usr/src/mypackage">
        <file>runit.sh</file>
        <find>BINDIR</find>
        <replace>/bin</replace>
</search_replace>

   The equivalent bash script is :
echo Performing substitution in runit.sh
cd /usr/src/mypackage
cp runit.sh /tmp/foo.$$
sed -e 's/BINDIR/\/bin/' /tmp/foo.$$ > runit.sh
     _________________________________________________________________

Element: <item>

Syntax


<!ELEMENT item           (#PCDATA)>

   This element occurs in the element : [289]Element: <list>

   See also : [290]Element : <description>
     _________________________________________________________________

Description

   The element item contains a item within a list in a description.
     _________________________________________________________________

Examples

<package name="gimp" version="1.2.3">
        <packageinfo>
                <description>
                    <para>The gimp package contains the GNU Image Manipulation
Program.
                    This is useful for :</para>
                    <list>
                    <item>photo retouching,</item>
                    <item>image composition,</item>
                    <item>image authoring.</item>
                    </list>
                </description>

                <requires><name>gtk+</name></requires>

                <utilizes><name>libtiff</name></utilizes>
                <utilizes><name>libpng</name></utilizes>
                <utilizes><name>libjpeg</name></utilizes>
                <utilizes><name>aalib</name></utilizes>
                <utilizes><name>mpeg_lib</name></utilizes>
                <utilizes><name>python</name></utilizes>

        </required>

        ....

    </package>

     _________________________________________________________________

Element: <link>

Syntax


<!ELEMENT link           (option?, target+, name)>
<!ATTLIST link
          base           CDATA #IMPLIED
          type           CDATA #IMPLIED>

   This element occurs in the elements : [291]Element : <alfs> |
   [292]Element: <stage>

   See also : [293]Element: <option> | [294]Element: <target> |
   [295]Element: <name>
     _________________________________________________________________

Description

   The element link is one of the many main operation elements. It allows
   you to create a hard or symbolic link.

   The sub-element target gives the name(s) of the targets.

   The sub-element option FILL IN HERE.

   The sub-element name gives the name of the link. When there are
   several targets, this must be the name of a directory, in which the
   links to the targets will be created.

   The attribute base specifies the directory in which the link creation
   is performed.

   The attribute type specifies if the link is symbolic (the attribute
   value is "symbolic" or not specified) or not (if the attribute value
   is "hard")

   The following two options are supported :
     * "force" means that the existing destination files are removed.
     * "no_dereference" means that if the destination is a symxref to a
       directory it will be treated as if it were a normal file (and thus
       will replace it if the "force" option is specified).
     _________________________________________________________________

Examples

<link>
        <target>share/man</target>
        <target>share/doc</target>
        <target>share/info</target>
        <name>/usr/local</name>
</link>

   The equivalent bash script is :
echo 'Linking  share/man share/doc share/info into /usr/local'
ln -s  share/man share/doc share/info /usr/local
     _________________________________________________________________

Element: <list>

Syntax


<!ELEMENT list           (item | list)+>
<!ATTLIST list
          type           (bullet | number) "bullet">

   This element occurs in the elements : [296]Element : <description>

   See also : [297]Element: <item>
     _________________________________________________________________

Description

   The element list contains a list of items or sub-lists in a
   description.
     _________________________________________________________________

Examples

<package name="gimp" version="1.2.3">
        <packageinfo>
                <description>
                <para>The gimp package contains the GNU Image Manipulation Prog
ram.
                        This is useful for :</para>
                <list>
                        <item>photo retouching,</item>
                        <item>image composition,</item>
                        <item>image authoring.</item>
                </list>
                </description>

                <requires><name>gtk+</name></requires>

                <utilizes><name>libtiff</name></utilizes>
                <utilizes><name>libpng</name></utilizes>
                <utilizes><name>libjpeg</name></utilizes>
                <utilizes><name>aalib</name></utilizes>
                <utilizes><name>mpeg_lib</name></utilizes>
                <utilizes><name>python</name></utilizes>

        </required>

        ....

</package>
     _________________________________________________________________

Element: <make>

Syntax


<!ELEMENT make           ((param | prefix)*)>
<!ATTLIST make
          base           CDATA #IMPLIED>

   This element occurs in the elements : [298]Element : <alfs> |
   [299]Element: <stage>

   See also : [300]Element: <param> | [301]Element: <prefix>
     _________________________________________________________________

Description

   The element make is one of the many main operation elements. It
   describes a make command.

   The sub-element param allows you to specify parameters of the make
   command.

   The sub-element prefix allows you to specify an environment variable
   or some other prefix to the make command

   The attribute base allows you to specify the directory in which the
   make will be performed.
     _________________________________________________________________

Examples

   The first example is a make without parameter
   <make />

   The equivalent bash script is :
echo Executing make
make

   The second example is a make with a parameter
<make base="/usr/src/mypackage">
        <param>install</param>
</make>

   The equivalent bash script is :
echo Executing make
cd /usr/src/mypackage
make install
     _________________________________________________________________

Element: <mkdir>

Syntax


<!ELEMENT mkdir          (option?, name+, permissions?)>
<!ATTLIST mkdir
          base           CDATA #IMPLIED>

   This element occurs in the elements : [302]Element : <alfs> |
   [303]Element: <stage>

   See also : [304]Element: <option> | [305]Element: <name> |
   [306]Element: <permissions>
     _________________________________________________________________

Description

   The element mkdir is one of the many main operation elements. It
   describes the creation of one (or several) directory(ies).

   The sub-element option FILL IN HERE.

   The sub-elements name contains the name(s) of the directory(ies) to be
   created.

   The sub-element permissions FILL IN HERE.

   The attribute base gives the name of the directory in which the new
   directory will be created.

   The only option supported is "parents". When specified, the parents
   directories are created as needed.
     _________________________________________________________________

Examples

<mkdir base="/usr/local/lib">
        <option>parents</option>
        <name>X11</name>
</mkdir>

   The equivalent bash script is :
cd /usr/local/lib
echo Making directory X11
mkdir -p X11
     _________________________________________________________________

Element: <move>

Syntax


<!ELEMENT move           (option?, source+, destination)>
<!ATTLIST move
             base           CDATA #IMPLIED>

   This element occurs in the elements : [307]Element : <alfs> |
   [308]Element: <stage> |

   See also : [309]Element: <option> | [310]Element: <source> |
   [311]Element: <destination>
     _________________________________________________________________

Description

   The element move is one of the many main operation elements. It is
   used to move one or several source files and/or directories into a
   destination file or directory.

   The sub-element option is an option of the mkdir command:
     * force

   .

   When processing this element, one moves each source to the
   destination, using the specified option if present.

   The sub-elements source contains the name(s) of the directory were the
   source file is.

   The sub-element destination contains the name of the destination
   directory for the mv command.

   The attribute base gives the name of the directory in which the new
   directory will be created.

   When the attribute base is specified, it should contain the name of
   the current directory from which the move operation is performed.
     _________________________________________________________________

Examples

<move>
        <source>/usr/src/mypackage/config.txt</source>
        <destination>/opt/mypackage/config.txt</destination>
</move>

   The equivalent bash script is :
echo Move ' /usr/src/mypackage/config.txt /opt/mypackage/config.txt'
mv /usr/src/mypackage/config.txt /opt/mypackage/config.txt
     _________________________________________________________________

Element: <name>

Syntax


<!ELEMENT name           (#PCDATA)>

   This element occurs in the elements : [312]Element: <link> |
   [313]Element: <mkdir> | [314]Element: <ownership> | [315]Element:
   <permissions> | [316]Element: <requires> | [317]Element: <utilizes>

   See also : [318]Element: <package> | [319]Element: <stage> |
   [320]Element: <variable>
     _________________________________________________________________

Description

   The element name is used to specify a name for some commands that
   requires it.
     _________________________________________________________________

Examples

<mkdir base="/usr/local/lib">
        <option>parents</option>
        <name>X11</name>
</mkdir>

   The equivalent bash script is :
cd /usr/local/lib
echo Making directory X11
mkdir -p X11
     _________________________________________________________________

Element: <option>

Syntax


<!ELEMENT option         (#PCDATA)>

   This element occurs in the elements : [321]Element : <copy> |
   [322]Element: <link> | [323]Element: <mkdir> | [324]Element: <move> |
   [325]Element: <ownership> | [326]Element: <permissions>
     _________________________________________________________________

Description

   The element option allows to specify an option of the englobing
   element.
     _________________________________________________________________

Examples

<mkdir base="/usr/local/lib">
        <option>parents</option>
        <name>X11</name>
</mkdir>

   The equivalent bash script is :
cd /usr/local/lib
echo Making directory X11
mkdir -p X11
     _________________________________________________________________

Element: <ownership>

Syntax


<!ELEMENT ownership      (option?, name+)>
<!ATTLIST ownership
             base           CDATA #IMPLIED
             user           CDATA #IMPLIED
             group          CDATA #IMPLIED>

   This element occurs in the elements : [327]Element : <alfs> |
   [328]Element: <stage>

   See also : [329]Element: <option> | [330]Element: <name>
     _________________________________________________________________

Description

   The element ownership is one of the many main operation elements. It
   is used to perform a group and/or user ownership change on a file or
   set of files

   The only option supported is "recursive"

   The sub-element name contains the name of the file (or directory)
   whose ownership is to be changed.

   The attribute base specifies the directory in which the command is
   performed.

   The attribute user specifies the name of the user which will own the
   file or directory

   The attribute group specifies the name of the group which will own the
   file or directory
     _________________________________________________________________

Examples

   The first example uses symbolic names.
<ownership user="root" group="root">
        <option>recursive</option>
        <name>/etc/rc.d</name>
        <name>/etc/sysconfig</name>
</ownership>

   The equivalent bash script is :
echo Changing group of /etc/rc.d into root
chgrp -R root /etc/rc.d

echo Changing owner of /etc/rc.d into root
chown -R root /etc/rc.d

echo Changing group of /etc/sysconfig into root
chgrp -R root /etc/sysconfig

echo Changing owner of /etc/sysconfig into root
chown -R root /etc/sysconfig

   The second example uses numeric values (0 = root).
<ownership user="0" group="0">
        <option>recursive</option>
        <name>/etc/rc.d</name>
        <name>/etc/sysconfig</name>
</ownership>

   The equivalent bash script is :
echo Changing group of /etc/rc.d into 0
chgrp -R 0 /etc/rc.d

echo Changing owner of /etc/rc.d into 0
chown -R 0 /etc/rc.d

echo Changing group of /etc/sysconfig into 0
chgrp -R 0 /etc/sysconfig

echo Changing owner of /etc/sysconfig into 0
chown -R 0 /etc/sysconfig
     _________________________________________________________________

Element: <package>

Syntax


<!ELEMENT package        (packageinfo?, stage+)>
<!ATTLIST package
             name           CDATA #REQUIRED
             version        CDATA #REQUIRED>

   This element occurs in the elements : [331]Element : <alfs> |
   [332]Element: <stage>

   See also : [333]Element: <packageinfo> | [334]Element: <stage>
     _________________________________________________________________

Description

   The element package is one of the many main operation elements. It
   describes the build process of a package.

   The actual build process is described by the stage sub-elements.

   The attribute name contains the name of the package.

   The attribute version contains the version of the package.
     _________________________________________________________________

Examples

<package name="zlib"
version="1.1.4">
        <stage name="Unpacking a package.">
                <unpack>
                        <archive>/usr/src/lfs-packages/zlib.1.1.4.tar.gz</archi
ve>
                        <destination>/usr/src</destination>
                </unpack>
        </stage>

        .....

</package>

   The equivalent bash script is :
echo Generating package zlib 1.1.4

#-----------------------------------------
echo Stage "Unpacking a package."

echo Unpacking /usr/src/lfs-packages/zlib.1.1.4.tar.gz into /usr/src
cd /usr/src
[[ $? != 0 ]] &&  echo Command failed && exit 3

tar xzvf /usr/src/lfs-packages/zlib.1.1.4.tar.gz
[[ $? != 0 ]] &&  echo Command failed && exit 3


echo Exiting stage "Unpacking a package."

...

echo End of generating package zlib 1.1.4
     _________________________________________________________________

Element: <packageinfo>

Syntax


<!ELEMENT packageinfo    (description?, requires*, utilizes*)>

   This element occurs in the element : [335]Element: <package>

   See also : [336]Element : <description> | [337]Element: <requires> |
   [338]Element: <utilizes>
     _________________________________________________________________

Description

   The element packageinfo groups elements containg information about the
   package, namely a description and some deopendency relationship.

   The description of the packge is contained in the description
   sub-element.

   The relationship "depends-on" is described by the requires
   sub-element.

   The relationship "will utilize" is described by the utilizes
   sub-element.
     _________________________________________________________________

Examples

   The equivalent bash script is :
echo Generating package zlib 1.1.4

#-----------------------------------------
echo Stage "Unpacking a package."

echo Unpacking /usr/src/lfs-packages/zlib.1.1.4.tar.gz into /usr/src
cd /usr/src
[[ $? != 0 ]] &&  echo Command failed && exit 3

tar xzvf /usr/src/lfs-packages/zlib.1.1.4.tar.gz
[[ $? != 0 ]] &&  echo Command failed && exit 3


echo Exiting stage "Unpacking a package."

...

echo End of generating package zlib 1.1.4
     _________________________________________________________________

Element: <para>

Syntax


<!ELEMENT para           (#PCDATA)>

   This element occurs in the elements : [339]Element : <description>
     _________________________________________________________________

Description

   The element para contains a paragraph of documentary text.
     _________________________________________________________________

Examples

<package name="gimp" version="1.2.3">
        <packageinfo;>
                <description;>
                        <para;>The gimp package contains the GNU Image Manipula
tion Program.
                        This is useful for photo retouching, image composition
and image authoring.
                        </para;>
                </description;>

                <requires;><name;>gtk+</name;></requires;>

                <utilizes;><name;>libtiff</name;></utilizes;>
                <utilizes;><name;>libpng</name;></utilizes;>
                <utilizes;><name;>libjpeg</name;></utilizes;>
                <utilizes;><name;>aalib</name;></utilizes;>
                <utilizes;><name;>mpeg_lib</name;></utilizes;>
                <utilizes;><name;>python</name;></utilizes;>

        </required;>

        ......

</package;>
     _________________________________________________________________

Element: <param>

Syntax


<!ELEMENT param          (#PCDATA)>

   This element occurs in the element : [340]Element : <configure> |
   [341]Element: <execute> | [342]Element: <make> | [343]Element: <patch>
     _________________________________________________________________

Description

   This element is used to specify a parameter of the element to which it
   belongs.
     _________________________________________________________________

Examples

<make>
        <param>install</param>
</make>

   The equivalent bash script is :
echo Executing make
make install
     _________________________________________________________________

Element: <patch>

Syntax


<!ELEMENT patch          ((param | prefix)*)>
<!ATTLIST patch
             base           CDATA #IMPLIED>

   This element occurs in the elements : [344]Element : <alfs> |
   [345]Element: <stage>

   See also : [346]Element: <param> | [347]Element: <prefix>
     _________________________________________________________________

Description

   The element patch is one of the many main operation elements. It is
   used to execute the patch command.

   The sub-elements param contain the parameters of the command.

   The attribute base specified the directory in which the command will
   be performed.
     _________________________________________________________________

Examples

<patch>
        <param>-N</param>
        <param>-p1</param>
        <param>-i ../gawk-3.1.1.patch</param>
</patch>

   The equivalent bash script is :
echo 'patch -N -p1 -i ../gawk-3.1.1.patch'
patch -N -p1 -i ../gawk-3.1.1.patch
     _________________________________________________________________

Element: <permissions>

Syntax


<!ELEMENT permissions    (option?, name+)>
<!ATTLIST permissions
             base           CDATA #IMPLIED
             mode           CDATA #REQUIRED>

   See also : [348]Element: <option> | [349]Element: <name>
     _________________________________________________________________

Description

   The element permissions is one of the many main operation elements. It
   allows one to change the permissions of a (set of) file(s) or
   directory(ies).

   The sub-element(s) name contain the name(s) of the files whose
   permission is to be modified.

   The attribute base gives the name of the directory in which the
   command will be performed

   The attribute mode gives the new access mode, as used in the command
   chmod.

   The only option supported is "recursive"
     _________________________________________________________________

Examples

<permissions mode="755">
    <name>/usr/bin/lex</name>
</permissions>

   The equivalent bash script is :
echo Changing permissions of /usr/bin/lex to 755
chmod 755 /usr/bin/lex
     _________________________________________________________________

Element: <prefix>

Syntax


<!ELEMENT prefix         (#PCDATA)>

   This element occurs in the elements : [350]Element : <configure> |
   [351]Element: <execute> | [352]Element: <make> | [353]Element: <patch>
     _________________________________________________________________

Description

   SECTION TO BE WRITTEN
     _________________________________________________________________

Examples

   SECTION TO BE WRITTEN
     _________________________________________________________________

Element: <reference>

Syntax


<!ELEMENT reference      (#PCDATA)>

   This element occurs in the element : [354]Element: <unpack>
     _________________________________________________________________

Description

   The element reference is used to specify the URL of the reference
   archive to download if the local copy is not available.
     _________________________________________________________________

Examples

<unpack>
        <reference>ftp://ftp.gnu.org/gnu/gzip/gzip.1.2.4a.tar.gz</reference>
        <archive>/usr/src/lfs-packages/gzip.1.2.4a</archive>
        <destination>/usr/src</destination>
</unpack>

   The equivalent bash script is :
echo Unpacking /usr/src/lfs-packages/gzip.1.2.4a.tar.gz into /usr/src
[[ ! -f /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ]] &&
  echo Retrieving  ftp://ftp.gnu.org/gnu/gzip/gzip.1.2.4a.tar.gz
[[ ! -f /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ]] &&
  wget -O /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ftp://ftp.gnu.org/gnu/gzip/g
zip.1.2.4a.tar.gz
[[ ! -f /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ]] &&
  echo Archive does not exist && exit 3

cd /usr/src
tar xzvf /usr/src/lfs-packages/gzip.1.2.4a.tar.gz
     _________________________________________________________________

Element: <remove>

Syntax


<!ELEMENT remove         (#PCDATA)>

   This element occurs in the elements : [355]Element : <alfs> |
   [356]Element: <stage>
     _________________________________________________________________

Description

   The element remove is one of the many main operation elements. It
   allows one to remove a file or directory. The content of the element
   contains the name of the file.

   The deletion of the directory is always recursive (rm -fr).
     _________________________________________________________________

Examples

   <remove>/usr/src/mypackage</remove>

   The equivalent bash script is :
echo Removing /usr/src/mypackage
rm -rf /usr/src/mypackage
     _________________________________________________________________

Element: <replace>

Syntax


<!ELEMENT replace        (#PCDATA)>

   This element occurs in the element : [357]Element: <search_replace>
     _________________________________________________________________

Description

   The element replace allows to specify the replacement string in a
   search and replace operation.
     _________________________________________________________________

Examples

<search_replace base="/usr/src/mypackage">
        <file>runit.sh</file>
        <find>BINDIR</find>
        <replace>/bin</replace>
</search_replace>

   The equivalent bash script is :
echo Performing substitution in runit.sh
cd /usr/src/mypackage
cp runit.sh /tmp/foo.$$
sed -e 's/BINDIR/\/bin/' /tmp/foo.$$ > runit.sh
     _________________________________________________________________

Element: <requires>

Syntax


<!ELEMENT requires       (name, version*)>

   This element occurs in the element : [358]Element: <packageinfo>

   See also : [359]Element: <name> | [360]Element: <version>
     _________________________________________________________________

Description

   The element requires denotes a dependency between two packages : the
   package containg the requires element depends on the package whose
   name is contained in the name sub-element.

   The actual name is put into a name element because we might want to
   add a version in a future version.
     _________________________________________________________________

Examples

<package name="librep" version="0.16.1">
        <packageinfo>
                <requires><name>gmp</name></requires>
                <requires><name>gdbm</name></requires>
        </packageinfo>

        <stage name="Unpacking a package.">
                <unpack>
                        <archive>librep-0.16.1/librep-0.16.1.tar.gz</archive>
                        <destination>/usr/src</destination>
                </unpack>
        </stage>

        ......

</package>

   The equivalent bash script is :
#-----------------------------------------
# processing package librep 0.16.1

echo Generating package librep 0.16.1

[[ ! -f ${NALFS_STAMP_DIR:-/var/log/nALFS}/gmp]] && echo Stamp of package gmp m
issing && exit 3
[[ ! -f ${NALFS_STAMP_DIR:-/var/log/nALFS}/gdbm]] && echo Stamp of package gdbm
 missing && exit 3

#-----------------------------------------
echo Stage "Unpacking a package."

echo Unpacking librep-0.16.1/librep-0.16.1.tar.gz into /usr/src
cd /usr/src
tar xzvf librep-0.16.1/librep-0.16.1.tar.gz

echo Exiting stage "Unpacking a package."

....

echo End of generating package librep 0.16.1
     _________________________________________________________________

Element: <root>

Syntax


<!ELEMENT root           (#PCDATA)>

   This element occurs in the element : [361]Element: <stageinfo>
     _________________________________________________________________

Description

   The element root allow to specify the name of a directory which will
   be the root directory for the commands of the stage.
     _________________________________________________________________

Examples

<stage>
        <stageinfo>
                <root>/mnt/lfs</root>
                <base>/usr/src/gzip.1.2.4a</base>
        </stageinfo>

        <configure />

        <make />

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Creating file /mnt/lfs/_nalfs_tmp.1...
cat > /mnt/lfs/_nalfs_tmp.1 << 'EOF1'
echo Executing configure
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
cd /usr/src/gzip.1.2.4a
make

echo Executing make
cd /usr/src/gzip.1.2.4a
make install

true
EOF1

chmod 775 /mnt/lfs/_nalfs_tmp.1
echo Executing in directory /mnt/lfs
/usr/sbin/chroot /mnt/lfs /static/bin/env -i \
    PATH='/bin:/usr/bin:/sbin:/usr/sbin:/static/bin' \
    HOME='/root' /static/bin/bash -c ./_nalfs_tmp.1

echo Exiting stage
     _________________________________________________________________

Element: <search_replace>

Syntax


<!ELEMENT search_replace (file, find, replace)>
<!ATTLIST configure
             base           CDATA #IMPLIED>

   This element occurs in the elements : [362]Element : <alfs> |
   [363]Element: <stage>

   See also : [364]Element: <file> | [365]Element: <find> | [366]Element:
   <replace>
     _________________________________________________________________

Description

   The element search_replace is one of the many main operation elements.
   It is used to perform a search and replace operation of a file.

   The sub-element file contains the filename

   The sub-element find contains the string to be searched

   The sub-element replace contains the replacement string.
     _________________________________________________________________

Examples

<search_replace base="/usr/src/mypackage">
        <file>runit.sh</file>
        <find>BINDIR</find>
        <replace>/bin</replace>
</search_replace>

   The equivalent bash script is :
echo Performing substitution in runit.sh
cd /usr/src/mypackage
cp runit.sh /tmp/foo.$$
sed -e 's/BINDIR/\/bin/' /tmp/foo.$$ > runit.sh
     _________________________________________________________________

Element: <source>

Syntax


<!ELEMENT source         (#PCDATA)>

   This element occurs in the elements : [367]Element : <copy> |
   [368]Element: <move>
     _________________________________________________________________

Description

   The element source is used to specify name of the source file when
   processing a [369]Element : <copy>, or a [370]Element: <move>.
     _________________________________________________________________

Examples

<copy base="/usr/src/mypackage">
        <option>force</option>
        <source>config.txt</source>
        <destination>/opt/mypackage/config.txt</destination>
</copy>

   The equivalent bash script is :
echo Copying 'config.txt into /opt/mypackage/config.txt'
cd /usr/src/mypackage
cp -f  config.txt /opt/mypackage/config.txt
     _________________________________________________________________

Element: <stage>

Syntax


<!ELEMENT stage          (stageinfo?, (alfs | configure | copy | download |
                             execute | link | make | mkdir | move | ownership |
                             package | patch | permissions | remove |
                             search_replace | stage | textdump | unpack)*)>
<!ATTLIST stage
             name           CDATA #IMPLIED>

   This element occurs in the elements : [371]Element : <alfs> |
   [372]Element: <stage>

   See also : [373]Element : <alfs> | [374]Element : <configure> |
   [375]Element : <copy> | [376]Element: <download> | [377]Element:
   <execute> | [378]Element: <link> | [379]Element: <make>> |
   [380]Element: <mkdir> | [381]Element: <move> | [382]Element:
   <ownership> | [383]Element: <package> | [384]Element: <patch> |
   [385]Element: <permissions> | [386]Element: <remove> | [387]Element:
   <search_replace> | [388]Element: <stageinfo> | [389]Element:
   <textdump> | [390]Element: <unpack>
     _________________________________________________________________

Description

   The element stage is one of the many main operation elements. It
   allows one to regroup commands, give a name to this group, through the
   attribute name, and optionally modify the execution context through
   the element stageinfo.
     _________________________________________________________________

Examples

<stage>
        <stageinfo>
                <base>/usr/src/gzip.1.2.4a</base>
        </stageinfo>

        <configure />

        <make />

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Executing configure
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
cd /usr/src/gzip.1.2.4a
make

echo Executing make
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage
     _________________________________________________________________

Element: <stageinfo>

Syntax


<!ELEMENT stageinfo      (root?, user?, environment?, base?)>

   This element occurs in the element : [391]Element: <stage>

   See also : [392]Element: <root> | [393]Element : <base> |
   [394]Element: <environment> | [395]Element: <user>
     _________________________________________________________________

Description

   The element stageinfo allows to specify several context informations
   used to process the commands of the stage to which the stageinfo
   belongs.

   The base sub-element specify a base directory that will be used by all
   the commands of the stage, unless that command redefines the base
   locally.

   The user sub-element specify a user name that will be used as the
   effective user ID of the current process for all the commands of the
   stage

   The root sub-element specify a directory name in which the commands of
   the stage will be performed (using a chroot command).

   The environment sub-element allow to specify a environment variable
   that will be added to the current environment when processing the
   commands of the stage.
     _________________________________________________________________

Examples

<stage>
        <stageinfo>
                <base>/usr/src/gzip.1.2.4a</base>
        </stageinfo>

        <configure />

        <make />

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Executing configure
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
cd /usr/src/gzip.1.2.4a
make

echo Executing make
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage
     _________________________________________________________________

Element: <target>

Syntax


<!ELEMENT target         (#PCDATA)>

   This element occurs in the element : [396]Element: <link>
     _________________________________________________________________

Description

   The element target describes a target of a link operation.
     _________________________________________________________________

Examples

<link>
        <target>share/man</target>
        <target>share/doc</target>
        <target>share/info</target>
        <name>/usr/local</name>
</link>

   The equivalent bash script is :
echo 'Linking  share/man share/doc share/info into /usr/local'
ln -s  share/man share/doc share/info /usr/local
     _________________________________________________________________

Element: <textdump>

Syntax


<!ELEMENT textdump       (file, content)>
<!ATTLIST textdump
             base           CDATA #IMPLIED
             mode           CDATA #IMPLIED>

   This element occurs in the elements : [397]Element : <alfs> |
   [398]Element: <stage>

   See also : [399]Element: <file> | [400]Element : <content>
     _________________________________________________________________

Description

   The element textdump is one of the many main operation elements. The
   sub-element file contains the name of the file to be created.

   The sub-element content is used to specify the content of the file
   being created when processing a textdump operation. When processing
   the textual content of this element, one removes the leading blanks up
   to and including a '=' character.

   The attribute base allows to specify the directory in which the file
   creation will be perforemd.

   The attribute mode allows to specify the append creation mode.
     _________________________________________________________________

Examples

<textdump base="/etc">
        <file>group</file>

        <content>
                =root:x:0:
                =bin:x:1:
                =sys:x:2:
                =kmem:x:3:
                =tty:x:4:
                =tape:x:5:
                =daemon:x:6:
                =floppy:x:7:
                =disk:x:8:
                =lp:x:9:
                =dialout:x:10:
                =audio:x:11:
        </content>
</textdump>

   The equivalent bash script is :
cd /etc
cat > group << 'EOF'
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:4:
tape:x:5:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
EOF

<textdump mode="append">
        <file>/etc/sysconfig/network</file>
        <content>
                =GATEWAY=192.168.123.254
                =GATEWAY_IF=eth0
        </content>
</textdump>

   The equivalent bash script is :
echo Generating file /etc/sysconfig/network
cat >> /etc/sysconfig/network << 'EOF'
GATEWAY=192.168.123.254
GATEWAY_IF=eth0
EOF
     _________________________________________________________________

Element: <unpack>

Syntax


<!ELEMENT unpack         (digest?, reference*, archive, destination)>

   This element occurs in the elements : [401]Element : <alfs> |
   [402]Element: <stage>

   See also : [403]Element : <archive> | [404]Element: <destination> |
   [405]Element: <digest> | [406]Element: <reference>
     _________________________________________________________________

Description

   The element unpack is one of the many main operation elements. It is
   used to unpack an archive into a destination directory

   The sub-element reference gives the URL of the archive, which is used
   if the archive file is not available locally.

   The sub-element digest gives the digest of the archive, as computed by
   openssl, using the digest type specified in the attribute type.

   The sub-element archive gives the name of the archive, and the
   sub-element destination given the name of the directory in which the
   archive is unpacked

   The choice of the program performing the unpacking is based on the
   extension of the archive file. The supported extensions are :
     * .tar.gz
     * .tar.bz2
     * .Z
     * .tgz
     * .gz
     * .bz2
     * .tar
     * .zip

     Note: The use of the sub-elements digest and reference is
     deprecated. You should use the element download instead.
     _________________________________________________________________

Examples

<unpack>
    <digest>cbe9f79450aeecfb06d5e856af16c2cf</digest>
    <reference>ftp://ftp.gnu.org/gnu/gzip/gzip.1.2.4a.tar.gz</reference>
    <archive>/usr/src/lfs-packages/gzip.1.2.4a.tar.gz</archive>
    <destination>/usr/src</destination>
</unpack>

   The equivalent bash script is :
echo Unpacking /usr/src/lfs-packages/gzip.1.2.4a.tar.gz into /usr/src
[[ ! -f /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ]] &&
  echo Retrieving  ftp://ftp.gnu.org/gnu/gzip/gzip.1.2.4a.tar.gz
[[ ! -f /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ]] &&
  wget -O /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ftp://ftp.gnu.org/gnu/gzip/g
zip.1.2.4a.tar.gz
[[ ! -f /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ]] &&
  echo Archive does not exist && exit 3

cd /usr/src
tar xzvf /usr/src/lfs-packages/gzip.1.2.4a.tar.gz
     _________________________________________________________________

Element: <url>

Syntax


<!ELEMENT url            (#PCDATA)>

   This element occurs in the elements : [407]Element: <download>
     _________________________________________________________________

Description

   The element url allows you to specify the Uniform Resource Locator
   (URL) of the directory containing the file to be downloaded when
   processing a download element.
     _________________________________________________________________

Examples

<download>
        <file>kbd-1.08.tar.gz</file>
        <url>ftp://ftp.win.tue.nl/pub/linux-local/utils/kbd/</url>
        <destination>/tmp/</destination>
        <digest>924e6a05e52715dc0f96385b35f2f680</digest>
</download>

   There is no equivalent Bash script example for this element.
     _________________________________________________________________

Element: <user>

Syntax


<!ELEMENT user           (#PCDATA)>

   This element occurs in the elements : [408]Element: <stageinfo>

   See also : [409]Element: <ownership>
     _________________________________________________________________

Description

   The element user allow to specify a user ID that will be the effective
   user ID when executing the commands of the stage to which it applies.
     _________________________________________________________________

Examples

<stage>
        <stageinfo>
                <base>/usr/src/mypackage</base>
                <user>lfs</user>
        </stageinfo>

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Stage

echo Creating file ./_nalfs_tmp.1...
cat > ./_nalfs_tmp.1 << 'EOF1'
echo Executing make
cd /usr/src/mypackage
make install

true
EOF1
[[ $? != 0 ]] &&  echo Creating file failed && exit 3

chmod 775 ./_nalfs_tmp.1
echo Executing as user lfs
/bin/su lfs -c ./_nalfs_tmp.1

echo Finished execution as user lfs

echo Exiting stage
     _________________________________________________________________

Element: <utilizes>

Syntax


<!ELEMENT utilizes       (name, version*)>

   This element occurs in the element : [410]Element: <packageinfo>

   See also : [411]Element: <name> | [412]Element: <version>
     _________________________________________________________________

Description

   The element utilizes indicates that the package containg the utilizes
   element utilizes the package whose name is contained in the name
   sub-element, but does not depend on it, in which case the element
   requires is used.

   The actual name is put into a name element because we might want to
   add a version in a future version.
     _________________________________________________________________

Examples

<package name="gimp" version="1.2.3">
<packageinfo>
        <requires><name>gtk+</name></requires>

                <utilizes><name>libtiff</name></utilizes>
                <utilizes><name>libpng</name></utilizes>
                <utilizes><name>libjpeg</name></utilizes>
                <utilizes><name>aalib</name></utilizes>
                <utilizes><name>mpeg_lib</name></utilizes>
                <utilizes><name>python</name></utilizes>

        </packageinfo>

        ....

</package>
     _________________________________________________________________

Element: <variable>

Syntax


<!ELEMENT variable       (#PCDATA)>
<!ATTLIST variable
             name           CDATA #REQUIRED
             mode           CDATA #IMPLIED>

   This element occurs in the element : [413]Element: <environment>
     _________________________________________________________________

Description

   The element variable allows to add a variable definition to the
   environment.

   The name of the variable is given by the attribute name of the
   element.

   The attribute mode can take the value "append", in which case the
   content of the element is appended to the value of the environment
   variable

   The value of the variable is given by the textual content of the
   element.
     _________________________________________________________________

Examples

<stage>
        <stageinfo>
                <base>/usr/src/gzip.1.2.4a</base>
                <environment>
                        <variable name="GCCFLAGS">-O2</variable>
                        <variable name="PATH" mode="append">:/opt/foo</variable
>
                </environment>
        </stageinfo>

        <configure />

        <make />

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Stage

export GCCFLAGS=-O2
export PATH=${PATH}:/opt/foo
echo Executing configure
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
cd /usr/src/gzip.1.2.4a
make

echo Executing make
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage
     _________________________________________________________________

Element: <version>

Syntax


<!ELEMENT version        (#PCDATA)>
<!ATTLIST version
          condition      (eq | ne | gt | ge | lt | le) #REQUIRED>

   This element occurs in the elements : [414]Element: <package> |
   [415]Element: <requires> | [416]Element: <utilizes>
     _________________________________________________________________

Description

   The element version describes a constraint on the version of an
   utilized or required package.

   The condition is satisfied if the comparison specified by the
   attribute condition applies between the actual version value of the
   package, and the value specified as the content of the element.

   When performing the comparison, the sequences of digits are compared
   numerically, while all the other characters are compared using their
   codes. Moreover, any substring is greater than the empty string.

   That means, for instance, that 2.0.10 is greater than 2.0.9, 2.0a is
   greater than 2.0 and 2.10 is greater than 2.1a.

   Note that the algorithm fails for reasonable interpretations of
   version numbers like 3.0 and 3.0beta. Intuitively, 3.0 is greater than
   3.0beta, but the algorithm returns the opposite. To indicate for
   instance that the required package must have a version greater than
   3.0, one would need two version elements, to require that the actual
   version be greater than or equal to 3.0, and that it be different from
   3.0beta.
     _________________________________________________________________

Examples

<packageinfo>
        <requires>
                <name>guile</name>
                <version condition="ge">1.5</version>
        </requires>
</packageinfo>

   This signifies that the package being build requires guile in its
   version 1.5 or more recent.

   There is no equivalent Bash script example for this element.

References

   1. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#preface
   2. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#preface-changelog
   3. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#preface-audience
   4. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#preface-contactinfo
   5. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN99
   6. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN109
   7. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN115
   8. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN126
   9. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#preface-acknowledgements
  10. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#preface-conventions
  11. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#alfs_dtd
  12. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#alfs_dtd-intro
  13. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
  14. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN200
  15. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN221
  16. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN243
  17. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_archive
  18. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN250
  19. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN255
  20. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN260
  21. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_base
  22. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN270
  23. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN275
  24. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN292
  25. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_configure
  26. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN304
  27. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN313
  28. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN334
  29. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_content
  30. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN362
  31. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN367
  32. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN376
  33. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_copy
  34. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN387
  35. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN397
  36. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN424
  37. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_description
  38. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN434
  39. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN442
  40. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN450
  41. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_destination
  42. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN457
  43. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN465
  44. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN474
  45. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_digest
  46. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN492
  47. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN498
  48. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN504
  49. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_download
  50. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN511
  51. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN522
  52. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN538
  53. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_environment
  54. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN545
  55. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN552
  56. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN558
  57. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_execute
  58. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN570
  59. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN579
  60. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN593
  61. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_file
  62. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN611
  63. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN618
  64. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN625
  65. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_find
  66. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN644
  67. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN649
  68. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN653
  69. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_item
  70. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN663
  71. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN670
  72. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN674
  73. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_link
  74. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN680
  75. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN690
  76. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN710
  77. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_list
  78. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN720
  79. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN727
  80. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN731
  81. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_make
  82. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN737
  83. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN746
  84. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN756
  85. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_mkdir
  86. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN774
  87. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN784
  88. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN797
  89. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_move
  90. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN807
  91. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN817
  92. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN837
  93. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_name
  94. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN847
  95. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN861
  96. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN865
  97. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_option
  98. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN875
  99. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN885
 100. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN889
 101. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_ownership
 102. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN899
 103. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN908
 104. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN921
 105. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_package
 106. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN945
 107. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN954
 108. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN964
 109. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_packageinfo
 110. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN973
 111. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN982
 112. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN992
 113. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_para
 114. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN999
 115. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1004
 116. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1008
 117. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_param
 118. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1014
 119. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1022
 120. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1025
 121. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_patch
 122. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1035
 123. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1044
 124. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1052
 125. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_permissions
 126. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1062
 127. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1068
 128. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1079
 129. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_prefix
 130. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1089
 131. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1097
 132. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1100
 133. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_reference
 134. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1105
 135. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1110
 136. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1114
 137. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_remove
 138. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1124
 139. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1130
 140. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1135
 141. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_replace
 142. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1145
 143. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1150
 144. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1154
 145. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_requires
 146. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1164
 147. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1172
 148. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1180
 149. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_root
 150. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1190
 151. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1195
 152. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1199
 153. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_search_replace
 154. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1208
 155. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1218
 156. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1228
 157. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_source
 158. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1238
 159. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1244
 160. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1250
 161. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 162. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1260
 163. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1285
 164. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1291
 165. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stageinfo
 166. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1303
 167. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1313
 168. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1325
 169. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_target
 170. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1337
 171. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1342
 172. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1346
 173. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_textdump
 174. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1356
 175. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1365
 176. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1377
 177. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_unpack
 178. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1391
 179. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1402
 180. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1434
 181. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_url
 182. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1444
 183. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1449
 184. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1454
 185. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_user
 186. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1461
 187. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1468
 188. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1472
 189. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_utilizes
 190. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1481
 191. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1489
 192. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1498
 193. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_variable
 194. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1504
 195. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1509
 196. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1519
 197. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_version
 198. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1528
 199. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1535
 200. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#AEN1545
 201. mailto:alfs-discuss@linuxfromscratch.org
 202. http://www.linuxfromscratch.org/mailman/listinfo/alfs-discuss
 203. mailto:alfs-log@linuxfromscratch.org
 204. http://www.linuxfromscratch.org/mailman/listinfo/alfs-log
 205. news:news.linuxfromscratch.org
 206. http://www.linuxfromscratch.org/
 207. http://www.linuxfromscratch.org/alfs
 208. mailto:jwrober@linuxfromscratch.org
 209. mailto:vassili@linuxfromscratch.org
 210. mailto:gerard@linuxfromscratch.org
 211. mailto:jwrober@linuxfromscratch.org
 212. http://www.linuxfromscratch.org/alfs
 213. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_configure
 214. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_copy
 215. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_download
 216. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_execute
 217. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_link
 218. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_make
 219. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_mkdir
 220. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_move
 221. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_ownership
 222. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_package
 223. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_patch
 224. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_permissions
 225. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_remove
 226. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_search_replace
 227. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 228. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_textdump
 229. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_unpack
 230. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_base
 231. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_unpack
 232. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stageinfo
 233. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 234. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_configure
 235. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_copy
 236. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_execute
 237. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_link
 238. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_make
 239. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_mkdir
 240. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_move
 241. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_ownership
 242. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_patch
 243. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_permissions
 244. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_search_replace
 245. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_textdump
 246. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 247. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 248. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_param
 249. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_prefix
 250. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_base
 251. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_textdump
 252. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 253. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 254. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_option
 255. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_source
 256. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_destination
 257. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_base
 258. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_packageinfo
 259. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_para
 260. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_list
 261. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_copy
 262. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_download
 263. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_move
 264. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_unpack
 265. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_copy
 266. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_move
 267. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_unpack
 268. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_download
 269. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_download
 270. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_unpack
 271. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 272. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 273. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_file
 274. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_url
 275. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_destination
 276. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_digest
 277. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_digest
 278. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stageinfo
 279. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_variable
 280. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 281. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 282. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_param
 283. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_prefix
 284. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_base
 285. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_download
 286. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_search_replace
 287. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_textdump
 288. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_search_replace
 289. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_list
 290. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_description
 291. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 292. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 293. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_option
 294. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_target
 295. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_name
 296. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_description
 297. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_item
 298. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 299. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 300. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_param
 301. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_prefix
 302. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 303. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 304. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_option
 305. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_name
 306. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_permissions
 307. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 308. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 309. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_option
 310. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_source
 311. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_destination
 312. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_link
 313. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_mkdir
 314. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_ownership
 315. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_permissions
 316. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_requires
 317. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_utilizes
 318. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_package
 319. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 320. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_variable
 321. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_copy
 322. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_link
 323. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_mkdir
 324. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_move
 325. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_ownership
 326. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_permissions
 327. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 328. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 329. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_option
 330. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_name
 331. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 332. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 333. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_packageinfo
 334. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 335. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_package
 336. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_description
 337. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_requires
 338. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_utilizes
 339. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_description
 340. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_configure
 341. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_execute
 342. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_make
 343. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_patch
 344. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 345. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 346. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_param
 347. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_prefix
 348. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_option
 349. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_name
 350. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_configure
 351. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_execute
 352. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_make
 353. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_patch
 354. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_unpack
 355. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 356. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 357. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_search_replace
 358. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_packageinfo
 359. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_name
 360. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_version
 361. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stageinfo
 362. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 363. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 364. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_file
 365. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_find
 366. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_replace
 367. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_copy
 368. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_move
 369. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_copy
 370. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_move
 371. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 372. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 373. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 374. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_configure
 375. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_copy
 376. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_download
 377. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_execute
 378. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_link
 379. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_make
 380. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_mkdir
 381. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_move
 382. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_ownership
 383. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_package
 384. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_patch
 385. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_permissions
 386. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_remove
 387. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_search_replace
 388. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stageinfo
 389. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_textdump
 390. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_unpack
 391. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 392. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_root
 393. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_base
 394. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_environment
 395. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_user
 396. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_link
 397. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 398. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 399. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_file
 400. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_content
 401. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_alfs
 402. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stage
 403. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_archive
 404. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_destination
 405. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_digest
 406. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_reference
 407. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_download
 408. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_stageinfo
 409. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_ownership
 410. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_packageinfo
 411. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_name
 412. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_version
 413. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_environment
 414. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_package
 415. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_requires
 416. file://localhost/home/jwrober/tmp/alfssyntaxdocbuild/ALFS-SYNTAX-DOC-CVS-NOHUNKS.html#elem_utilizes
