
   #[1]ALFS DTD [2]Preface

ALFS DTD

Version 3.1-2004-06-05

ALFS DTD Development Team

   Copyright  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.

   Abstract

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

Dedication

   This book is dedicated to the LFS and ALFS communities.

   Table of Contents

   [3]Preface

        [4]ChangeLog
        [5]Who Would Want To Read This Book
        [6]Contact Information

              [7]Mailing Lists
              [8]News Server
              [9]WWW Links
              [10]Other

        [11]Acknowledgements
        [12]Conventions Used In This Book

   1. [13]Description of the ALFS Profile Syntax

        [14]ALFS DTD Introduction
        [15]XML & DTD Syntax

              [16]Quick Introduction to XML Syntax
              [17]Standard Entities
              [18]XML Elements and Attributes
              [19]Quick Introduction to DTD Syntax
              [20]DTD Element Declaration
              [21]DTD Attribute Declaration
              [22]DOCTYPE and SYSTEM Declarations

        [23]Element : <alfs>

              [24]Syntax
              [25]Description
              [26]Examples

        [27]Element : <archive>

              [28]Syntax
              [29]Description
              [30]Examples

        [31]Element : <base>

              [32]Syntax
              [33]Description
              [34]Examples

        [35]Element : <configure>

              [36]Syntax
              [37]Description
              [38]Example #1
              [39]Example #2
              [40]Example #3
              [41]Example #4

        [42]Element : <content>

              [43]Syntax
              [44]Description
              [45]Examples

        [46]Element : <copy>

              [47]Syntax
              [48]Description
              [49]Examples

        [50]Element : <description>

              [51]Syntax
              [52]Description
              [53]Examples

        [54]Element: <destination>

              [55]Syntax
              [56]Description
              [57]Example #1
              [58]Example #2

        [59]Element: <digest>

              [60]Syntax
              [61]Description
              [62]Examples

        [63]Element: <download>

              [64]Syntax
              [65]Description
              [66]Examples

        [67]Element: <environment>

              [68]Syntax
              [69]Description
              [70]Examples

        [71]Element: <execute>

              [72]Syntax
              [73]Description
              [74]Example #1
              [75]Example #2

        [76]Element: <file>

              [77]Syntax
              [78]Description
              [79]Examples

        [80]Element: <find>

              [81]Syntax
              [82]Description
              [83]Examples

        [84]Element: <include>

              [85]Syntax
              [86]Description
              [87]Examples

        [88]Element: <item>

              [89]Syntax
              [90]Description
              [91]Examples

        [92]Element: <link>

              [93]Syntax
              [94]Description
              [95]Examples

        [96]Element: <list>

              [97]Syntax
              [98]Description
              [99]Examples

        [100]Element: <make>

              [101]Syntax
              [102]Description
              [103]Example #1
              [104]Example #2

        [105]Element: <mkdir>

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

        [109]Element: <move>

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

        [113]Element: <name>

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

        [117]Element: <option>

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

        [121]Element: <ownership>

              [122]Syntax
              [123]Description
              [124]Example #1
              [125]Example #2

        [126]Element: <package>

              [127]Syntax
              [128]Description
              [129]Examples

        [130]Element: <packageinfo>

              [131]Syntax
              [132]Description
              [133]Examples

        [134]Element: <para>

              [135]Syntax
              [136]Description
              [137]Examples

        [138]Element: <param>

              [139]Syntax
              [140]Description
              [141]Examples

        [142]Element: <patch>

              [143]Syntax
              [144]Description
              [145]Examples

        [146]Element: <permissions>

              [147]Syntax
              [148]Description
              [149]Examples

        [150]Element: <prefix>

              [151]Syntax
              [152]Description
              [153]Examples

        [154]Element: <reference>

              [155]Syntax
              [156]Description
              [157]Examples

        [158]Element: <remove>

              [159]Syntax
              [160]Description
              [161]Examples

        [162]Element: <replace>

              [163]Syntax
              [164]Description
              [165]Examples

        [166]Element: <requires>

              [167]Syntax
              [168]Description
              [169]Examples

        [170]Element: <root>

              [171]Syntax
              [172]Description
              [173]Examples

        [174]Element: <search_replace>

              [175]Syntax
              [176]Description
              [177]Examples

        [178]Element: <source>

              [179]Syntax
              [180]Description
              [181]Examples

        [182]Element: <stage>

              [183]Syntax
              [184]Description
              [185]Examples

        [186]Element: <stageinfo>

              [187]Syntax
              [188]Description
              [189]Examples

        [190]Element: <target>

              [191]Syntax
              [192]Description
              [193]Examples

        [194]Element: <textdump>

              [195]Syntax
              [196]Description
              [197]Example #1
              [198]Example #2

        [199]Element: <unpack>

              [200]Syntax
              [201]Description
              [202]Examples

        [203]Element: <url>

              [204]Syntax
              [205]Description
              [206]Examples

        [207]Element: <user>

              [208]Syntax
              [209]Description
              [210]Examples

        [211]Element: <utilizes>

              [212]Syntax
              [213]Description
              [214]Examples

        [215]Element: <variable>

              [216]Syntax
              [217]Description
              [218]Examples

        [219]Element: <version>

              [220]Syntax
              [221]Description
              [222]Examples

Preface

ChangeLog

   3.1-2004-06-05 - Jube 5th, 2004
     * June 5th, 2004 [jwrober]: Updates from Kevin Fleming.
     * June 4th, 2004 [jwrober]: Added missing elem_include element.
     * June 4th, 2004 [jwrober]: Following other suggestions from Richard
       Downing's proofreading; modified the contruction "this allows one
       to..." to "this allows you to...".
     * June 3rd, 2004 [jwrober]: Applied patch with some modifications
       from Richard Downing's proofreading.
     * May 31st, 2004 [jwrober]: Removed Unused XML Tags from the source.
     * May 29th, 2004 [jwrober]: With some help from Manuel Canales
       Esparcia, modified the no-chunks xsl file to support inline css
       styling.
     * May 29th, 2004 [jwrober]: Upgraded to DocBook v4.3 and some other
       little nagging bugs fixes in the render.
     * May 28th, 2004 [jwrober]: Updated in elem_patch to include element
       prefix -- Bug 766.
     * May 28th, 2004 [jwrober]: Updated in elem_make to include element
       prefix -- Bug 764.
     * May 28th, 2004 [jwrober]: Updated in elem_execute to include
       element prefix -- Bug 762.
     * May 28th, 2004 [jwrober]: Updated in elem_configure and
       elem_prefix for correct bash examples -- Bug 757.
     * May 28th, 2004 [jwrober]: Filled in elem_prefix page -- Bug 802.
     * May 28th, 2004 [jwrober]: Updated alfs.css the rest of the element
       files to support better formatting of examples.
     * May 28th, 2004 [jwrober]: Cleaned up elem_archive, elem_configure,
       elem_copy, elem_description, elem_destination, elem_digest,
       elem_download, elem_environment, elem_execute, elem_file,
       elem_find, elem_item, elem_link, elem_list, elem_make, elem_mkdir,
       elem_move, elem_name, elem_ownership, elem_package,
       elem_packageinfo, elem_para, elem_param, elem_patch,
       elem_permissions, elem_remove, elem_replace, elem_requires,
       elem_search_replace, elem_source, elem_stage, elem_stageinfo,
       elem_target, elem_textdump, elem_url, elem_user, elem_utilizes,
       elem_variable.
     * April 2nd, 2004 [jwrober]: Cleaned up elem_alfs, elem_archive,
       elem_base, elem_configure, and part of elem_stageinfo.
     * April 2nd, 2004 [jwrober]: Added more formatting to the XML DTD
       intro page to match conventions.
     * April 2nd, 2004 [jwrober]: Added note to the conventions page.
     * March 30th, 2004 [jwrober]: Removed the implementation specific
       information in elem_unpack -- Bug 768.
     * March 30th, 2004 [jwrober]: Removed the note about elem_digest and
       elem_reference being deprecated in the DTD -- Bug 767.
     * March 30th, 2004 [jwrober]: Added info about the parents option to
       elem_mkdir -- Bug 765.
     * March 30th, 2004 [jwrober]: Finished the XML and DTD syntax intro
       -- Bug 784.
     * March 15th, 2004 [jwrober]: Added more to the XML and DTD syntax
       intro -- Bug 784.
     * March 14th, 2004 [jwrober]: Added an initial stab at an XML and
       DTD syntax intro -- Bug 784.
     * February 23rd, 2004 [jwrober]: Finished the elem_download
       description -- Bug 760.
     * February 23rd, 2004 [jwrober]: Finished the elem_url description
       -- Bug 769.
     * February 23rd, 2004 [jwrober]: Finished the elem_digest
       description -- Bug 759.
     * February 23rd, 2004 [jwrober]: Fixed elem_copy description -- Bug
       758.
     * February 23rd, 2004 [jwrober]: Fixed wierd character in
       acknowledgements page -- 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
   [223]alfs-discuss@linuxfromscratch.org. This is an excellent place to
   post questions and bug reports. For complete mailing list information,
   refer to
   [224]http://www.linuxfromscratch.org/mailman/listinfo/alfs-discuss.

   The second list is really for the development team's use and is
   available at [225]alfs-log@linuxfromscratch.org. This is an excellent
   place to see the daily activity of the project. For complete mailing
   list information, refer to
   [226]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 [227]news.linuxfromscratch.org.

WWW Links

   Some other xrefs that might interest you:

   Linux From Scratch:

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

   Automated Linux From Scratch:

     [229]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
   [230]jwrober@linuxfromscratch.org.

Acknowledgements

   We would like to thank the following people and organizations for
   their contributions towards the Automated Linux From Scratch project:
     * [231]Vassili Dzuba <vassili@linuxfromscratch.org> -- for helping
       to create the DTD and writing the intial version of this book.
     * [232]Gerard Beekmans <gerard@linuxfromscratch.org> -- for being
       more then a great help.
     * [233]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

   Bold Emphasis

     These forms of text are used for several purposes in the book but
     mainly to emphasize important points or to give examples as to what
     to type.

   [234]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.

Note

   Sample Note

     This type of section is to define a notice of some kind. Mostly to
     alert you of something to take note of.

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)

XML & DTD Syntax

Quick Introduction to XML Syntax

   To ensure that all readers of the ALFS DTD Book get as much as
   possible from its contents, it is necessary to provide a quick
   introduction to the concepts of XML and DTD syntax.

Note

   This introduction provides very few examples. This book is written in
   an XML DTD called DocBook XML. For an example of XML just look at the
   book's source. Since this book is documenting an XML DTD, look at the
   rest of the book's contents for examples of DTD syntax.

   To begin, here are some basic rules of XML :
     * XML documents use a self-describing and simple to use syntax.
     * All XML elements must have a closing tag. With XML, it is illegal
       to omit the closing tag.
     * XML tags are case sensitive.
     * All XML elements must be properly nested. Improper nesting of tags
       makes no sense to XML.
     * All XML documents must have a root element. In other words, all
       XML documents must contain a single tag pair to define a root
       element.
     * Attribute values must always be quoted. With XML, it is illegal to
       omit quotation marks around attribute values.
     * XML parsers preserve all whitespace in XML documents, even that
       which is considered non-significant.
     * The use of the ampersand [ & ] symbol is reserved. XML uses this
       to define an entity reference.

Standard Entities

   As mentioned in the last section, the ampersand symbol cannot be used
   by itself. There are a set of standard entity references that every
   DTD file should contain. There are mostly symbols that you would want
   to place inside the XML file. You define them by using thier decimal
   value on the ASCII chart. Here is a good list :
     * Less-Than [ < ] : "&#60;"
     * Greater-Than [ > ] : "&#62;"
     * Ampersand [ & ] : "&#38;"
     * Apostrophe [ ' ] : "&#39;"
     * Quote [ " ] : "&#34;"
     * Non Breaking Space (a forced space) : "&#32;"
     * Emdash [ -- ] : "&#045;&#045;"

XML Elements and Attributes

   XML is designed to hold any kind of information. This information is
   stored in Elements. Elements are the basic building blocks of XML and
   are represented in a XML document as tag pairs. Attributes provide a
   mechanism to further define or classify an element. Elements have
   relationships with other elements in a document. Some are parents and
   some are children. Using this semantic description, one can see that
   children elements need parent elements defined and used first. As
   mentioned in the last section, an XML document must have a root
   element. Think of this as the ultimate parent element. The root
   element must be defined and used before all other elements and all
   sub-elements (children). All elements and sub-elements will reside
   inside of the root element. An element can have parsed content, mixed
   content, simple content, empty content or attributes in their
   definition.

   XML elements must follow these naming rules :
     * Names can contain letters, numbers, and other characters
     * Names must not start with a number or punctuation character
     * Names must not start with the letters xml (or XML or Xml ...)
     * Names cannot contain spaces

Quick Introduction to DTD Syntax

   Once an XML document is written, it is generally a good idea to
   validate the elements used in the document against a known DTD. The
   Document Type Definition is the mechanism with which one validates the
   content of a well-formed XML document.

   XML DTD files contain :
     * Element declarations and definitions : Elements are declared and
       defined with their relationships in the DTD file.
     * Attribute declarations and definitions : Element classes or
       attributes are declared and defined in the DTD file.
     * Entities : Entities are the same thing as variables inside a DTD
       file or XML document. They can hold any kind of data.
     * PCDATA : PCDATA is Parsed Character DATA. PCDATA is text that will
       be parsed by a parser. Tags inside the text will be treated as
       markup and entities will be expanded.
     * CDATA : CDATA is Character DATA. CDATA is text that will NOT be
       parsed by a parser. Tags inside the text will NOT be treated as
       markup and entities will not be expanded.

DTD Element Declaration

   Elements are declared in the DTD file using a simple, but strict
   syntax. There are four ways to define an element :
     * EMPTY : When an element is declared with the EMPTY keyword, it
       means that the element will not hold any information. This is
       generally used for special tags like <br>.
     * ANY : When an element is declared with the ANY keyword, it means
       that the element can contain any information that the author wants
       it to. This is generally a special case.
     * Character Data : When an element is declared with either the
       PCDATA or CDATA keywords, it will hold one of the two types of
       information described above.
     * With Children : When an element is declared with the names of
       other elements in it, this defines a parent-child relationship.
       Look in the DTD for the child element names to be further defined
       with the other three ways.
     * Mixed : Some combination of the above four. Generally this is
       character data mixed with children.

   When an element is declared with children, it will also define how the
   children can be used inside an XML document and also in the order that
   they are allowed to appear in an XML document. There are four ways
   that children elements can be defined in a DTD file :
     * One Occurance Only : Example : [235]Element: <search_replace>. The
       child elements of <search_replace> -- <file>, <find>, and
       <replace> can only be used once. Notice that there are no symbols
       after any of the child element names. This is the identifier.
     * Minimum of One Occurance : Example : [236]Element: <permissions>.
       One of the child elements of <permissions> -- <name>, must be used
       a minimum of once, but can also be used many times. Notice the
       plus [ + ] symbol after the name. This is the identifier.
     * Zero or More Occurances : Example : [237]Element: <download>. One
       of the child elements of <download> -- <url>, can be used zero or
       many times. Notice the asterisk [ * ] symbol after the name. This
       is the identifier.
     * Zero or One Occurance : Example : [238]Element: <download>. One of
       the child elements of <download> -- <digest>, can be used zero or
       one time only. Notice the question mark [ ? ] symbol after the
       name. This is the identifier.
     * Either / Or Occurances : Example : [239]Element: <execute>. One of
       the two child elements of <execute> -- <param>, or <prefix>, can
       only be used. Notice the pipe [ | ] symbol in between the two
       elements. This is the identifier.

DTD Attribute Declaration

   As mentioned above, attributes can help to define "classes" of
   Elements. Attributes are defined with types and values. There are 11
   types :
     * CDATA : The value is Character Data.
     * (en1|en2|...) : The value is an enumerated list.
     * ID : The value is a unique id.
     * IDREF : The value is the id of another element.
     * IDREFS : The value is a list of other ids,
     * NMTOKEN : The value is a valid XML name.
     * NMTOKENS : The value is a list of valid XML names.
     * ENTITY : The value is an entity.
     * ENTITIES : The value is a list of entities.
     * NOTATION : The value is a name of a notation.
     * xml : The value is a predefined XML value.

   There are four value options :
     * Value : The default value of the attribute surrounded by quotes [
       " " ]. Example : [240]Element : <alfs>.
     * #IMPLIED : The attribute is optional. Example : [241]Element :
       <alfs>.
     * #REQUIRED : The attribute is required when the element is used.
       Example : [242]Element: <execute>.
     * #FIXED : A fixed value. Used with the Value option. Example :
       [243]Element : <alfs>.

DOCTYPE and SYSTEM Declarations

   The DOCTYPE declaration is used in an XML document to define to the
   XML parser what DTD should be referenced. This declaration is helpful
   when you have a seperate DTD file outside of the XML document. See
   [244]Element : <alfs> for an example.

   The SYSTEM declaration is used in an XML document to give provide a
   way to split up a file into smaller chunks. Many XML files can be
   quite large and having all the information inside one file can be
   unwieldy. The SYSTEM declaration works just like any ENTITY
   declaration. See [245]Element : <alfs> for an example.

Element : <alfs>

Syntax

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

   See also : [246]Element : <configure> | [247]Element : <copy> |
   [248]Element: <download> | [249]Element: <execute> | [250]Element:
   <link> | [251]Element: <make> | [252]Element: <mkdir> | [253]Element:
   <move> | [254]Element: <ownership> | [255]Element: <package> |
   [256]Element: <patch> | [257]Element: <permissions> | [258]Element:
   <remove> | [259]Element: <search_replace> | [260]Element: <stage> |
   [261]Element: <textdump> | [262]Element: <unpack> | [263]Element:
   <include>

Description

   The element alfs is the root element of an ALFS Profile document. 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 occurrence.

   The attribute base is used to specify the base directory which will be
   used by all the commands in the element alfs. See [264]Element :
   <base>.

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

   The element include and the attributes xml:base and xmlns:xi allow you
   to use xi:include directives in your profiles.

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 : [265]Element: <unpack>.

Description

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

Examples

   Refer to [266]Element: <unpack> for an example.

Element : <base>

Syntax

<!ELEMENT base           (#PCDATA)>

   This element occurs in : [267]Element: <stageinfo>

   This element occurs as an attribute in the elements : [268]Element :
   <alfs> | [269]Element : <configure> | [270]Element : <copy> |
   [271]Element: <execute> | [272]Element: <link> | [273]Element: <make>
   | [274]Element: <mkdir> | [275]Element: <move> | [276]Element:
   <ownership> | [277]Element: <patch> | [278]Element: <permissions> |
   [279]Element: <search_replace> | [280]Element: <textdump>

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.

Examples

<stage name="Install gzip">

        <stageinfo>

                <root>/mnt/lfs</root>
                <user>lfs</user>
                <environment>
                        <variable name="PATH">/bin:/sbin</variable>
                </environment>
                <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 Executing configure
su - lfs
export PATH=/bin:/sbin
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
su - lfs
export PATH=/bin:/sbin
cd /usr/src/gzip.1.2.4a
make

echo Executing make
su - lfs
export PATH=/bin:/sbin
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage

Element : <configure>

Syntax

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

   This element occurs in : [281]Element : <alfs> | [282]Element: <stage>

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

Description

   The element configure is one of the top-level operation elements. The
   element configure is used to describe the command configure.

   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 [285]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.

Example #1

   This first 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

Example #2

   This second 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

Example #3

   This third example calls configure with a parameter and uses prefix :
<configure base="/usr/src/mypackage/">
        <prefix>PATH=/usr/local/bin</prefix>
        <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

Example #4

   This fourth example calls configure with a parameter and an explicit
   command (same result as example #3) :
<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 : [286]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 occurs in : [287]Element : <alfs> | [288]Element: <stage>

   See also : [289]Element: <option> | [290]Element: <source> |
   [291]Element: <destination>

Description

   The element copy is one of the top-level operation elements. It is
   used to copy a file and/or directory into a destination file or
   directory.

   The sub-element option provides a means to pass an option to the cp
   command.

Note

   Not all of the cp options are in every implementation. Refer to the
   documentation for your implementation to determine what options are
   available.

   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 [292]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 : [293]Element: <packageinfo>

   See also : [294]Element: <para> | [295]Element: <list>

Description

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

Examples

   Refer to [296]Element: <packageinfo> for an example.

   There is no equivalent Bash script example for this element.

Element: <destination>

Syntax

<!ELEMENT destination    (#PCDATA)>

   This element occurs in : [297]Element : <copy> | [298]Element:
   <download> | [299]Element: <move> | [300]Element: <unpack> |

Description

   The element destination is used to specify the name of the destination
   file or directory when processing an element in which it occurs

Example #1

   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

Example #2

   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 ; [301]Element: <download> | [302]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

   Refer to [303]Element: <reference> for an example.

   There is no equivalent Bash script example for this element.

Element: <download>

Syntax

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

   This element occurs in : [304]Element : <alfs> | [305]Element: <stage>

   See also : [306]Element: <file> | [307]Element: <url> | [308]Element:
   <destination> | [309]Element: <digest>

Description

   The element download is one of the top-level 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 is 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.

   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. See [310]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>gzip-1.2.4a.tar.gz</file>
        <url>ftp://gnu.org/</url>
        <destination>/tmp/</destination>
        <digest>924e6a05e52715dc0f96385b35f2f680</digest>
</download>

   The equivalent bash script is :
echo Executing 'download'
wget -nc -O /tmp/gzip-1.2.4a.tar.gz ftp://gnu.org/gzip-1.2.4a.tar.gz

Element: <environment>

Syntax

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

   This element occurs in : [311]Element: <stageinfo>

   See also : [312]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:</variable>
                        <variable name="LDFLAGS" mode="append"> -s</variable>
                </environment>

        </stageinfo>

</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 Exiting stage

Element: <execute>

Syntax

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

   This element occurs in : [313]Element : <alfs> | [314]Element: <stage>

   See also : [315]Element: <param> | [316]Element: <prefix>

Description

   The element execute is one of the top-level operation elements. It is
   used to execute any arbitrary system command.

   The sub-element param contains parameters for the command.

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

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

   The attribute command contains the text of the command itself.

Example #1

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

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

Example #2

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

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

Element: <file>

Syntax

<!ELEMENT file           (#PCDATA)>

   This element occurs in : [318]Element: <download> | [319]Element:
   <search_replace> | [320]Element: <textdump>.

Description

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

Examples

   See any one of the parent elements for an example.

Element: <find>

Syntax

<!ELEMENT find           (#PCDATA)>

   This element occurs in : [321]Element: <search_replace>

Description

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

Examples

   Refer to the parent [322]Element: <search_replace> for an example.

Element: <include>

Syntax

<!ELEMENT include        EMPTY>
<!ATTLIST include
          href           CDATA #REQUIRED>

   This element occurs in : [323]Element : <alfs>

Description

   The element include contains data necessary to handle the xi:include
   directive in an alfs element.

Examples

   Refer to [324]Element : <alfs> for an example.

Element: <item>

Syntax

<!ELEMENT item           (#PCDATA)>

   This element occurs in : [325]Element: <list>

Description

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

Examples

   Refer to [326]Element : <description> for an example.

Element: <link>

Syntax

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

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

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

Description

   The element link is one of the top-level operation elements. It allows
   you to create a hard or symbolic link.

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

   The sub-element option provides a means to pass an option to the ln
   command.

Note

   Not all of the ln options are in every implementation. Refer to the
   documentation for your implementation to determine what options are
   available.

   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. See [332]Element : <base>.

   The attribute type generally can have one of two values: symbolic or
   hard to go along with how the ln works.

Examples

<link type="symbolic">
        <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 : [333]Element : <description>

   See also : [334]Element: <item>

Description

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

   The attribute type provides a way to define a numbered or bulleted
   list

Examples

   Refer to the parent [335]Element : <description> for an example.

Element: <make>

Syntax

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

   This element occurs in : [336]Element : <alfs> | [337]Element: <stage>

   See also : [338]Element: <param> | [339]Element: <prefix>

Description

   The element make is one of the top-level operation elements. It
   describes the 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. See [340]Element : <base>.

Example #1

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

   The equivalent bash script is :
echo Executing make
make

Example #2

   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 : [341]Element : <alfs> | [342]Element: <stage>

   See also : [343]Element: <option> | [344]Element: <name> |
   [345]Element: <permissions>

Description

   The element mkdir is one of the top-level operation elements. It
   describes the creation of one (or several) directory(ies).

   The sub-element option provides a means to pass an option to the mkdir
   command.

Note

   Not all of the mkdir options are in every implementation. Refer to the
   documentation for your implementation to determine what options are
   available.

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

   The sub-element permissions assigns permissions to the directories
   created by the command following the syntax in [346]Element:
   <permissions>.

   The attribute base gives the name of the directory in which the new
   directory will be created. See [347]Element : <base>.

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 : [348]Element : <alfs> | [349]Element: <stage>
   |

   See also : [350]Element: <option> | [351]Element: <source> |
   [352]Element: <destination>

Description

   The element move is one of the top-level 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 provides a means to pass an option to the mv
   command.

Note

   Not all of the mv options are in every implementation. Refer to the
   documentation for your implementation to determine what options are
   available.

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

   The sub-element source contains the name of the source file and its
   directory.

   The sub-element destination contains the name of the destination
   directory (and, optionally, the filename) for the mv command.

   The attribute base gives the name of the directory in which the new
   directory will be created. See [353]Element : <base>.

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 : [354]Element: <link> | [355]Element: <mkdir>
   | [356]Element: <ownership> | [357]Element: <permissions> |
   [358]Element: <requires> | [359]Element: <utilizes>

   See also (used as an attribute) : [360]Element: <package> |
   [361]Element: <stage> | [362]Element: <variable>

Description

   The element name is used to specify a name for those 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 : [363]Element : <copy> | [364]Element: <link>
   | [365]Element: <mkdir> | [366]Element: <move> | [367]Element:
   <ownership> | [368]Element: <permissions>

Description

   The element option allows you to specify an option of the parent
   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 : [369]Element : <alfs> | [370]Element: <stage>

   See also : [371]Element: <option> | [372]Element: <name>

Description

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

   The sub-element option provides a means to pass an option to the chown
   command.

Note

   Not all of the chown options are in every implementation. Refer to the
   documentation for your implementation to determine what options are
   available.

   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. See [373]Element : <base>.

   The attribute user specifies the name of the user which will own the
   file or directory. See [374]Element: <user>.

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

Example #1

   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

Example #2

   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 : [375]Element : <alfs> | [376]Element: <stage>

   See also : [377]Element: <packageinfo> | [378]Element: <stage>

Description

   The element package is one of the top-level 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. See [379]Element:
   <name>.

   The attribute version contains the version of the package. See
   [380]Element: <version>.

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 : [381]Element: <package>

   See also : [382]Element : <description> | [383]Element: <requires> |
   [384]Element: <utilizes>

Description

   The element packageinfo groups elements containing information about
   the package, namely a description and some dependency relationship(s).

   The description sub-element provides for a description of the packge.

   The requires sub-element provides for a relationship (dependancy) to
   other defined packages in the profile.

   The utilizes sub-element provdes for a relationship (uses / optional)
   to other defined packages in the profile.

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 :</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>

        </packageinfo>

        ....

</package>

   There is no equivalent bash script for the element.

Element: <para>

Syntax

<!ELEMENT para           (#PCDATA)>

   This element occurs in : [385]Element : <description>

Description

   The element para contains a paragraph of documentary text.

Examples

   Refer to [386]Element: <packageinfo> for an example.

Element: <param>

Syntax

<!ELEMENT param          (#PCDATA)>

   This element occurs in : [387]Element : <configure> | [388]Element:
   <execute> | [389]Element: <make> | [390]Element: <patch>

Description

   This element is used to specify a parameter of the parent element.

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 : [391]Element : <alfs> | [392]Element: <stage>

   See also : [393]Element: <param> | [394]Element: <prefix>

Description

   The element patch is one of the top-level operation elements. It is
   used to execute the patch command.

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

   The sub-element prefix provides a means to specify an environment
   variable or some other prefix to the patch 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 : [395]Element: <option> | [396]Element: <name>

Description

   The element permissions is one of the top-level operation elements. It
   allows you to change the permissions of a (set of) file(s) or
   directory(ies).

   The sub-element option provides a means to pass an option to the chmod
   command.

Note

   Not all of the chmod options are in every implementation. Refer to the
   documentation for your implementation to determine what options are
   available.

   The sub-element(s) name contain the name(s) of the files whose
   permission is to be modified. See [397]Element: <name>.

   The attribute base gives the name of the directory in which the
   command will be performed. See [398]Element : <base>.

   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 : [399]Element : <configure> | [400]Element:
   <execute> | [401]Element: <make> | [402]Element: <patch>

Description

   The element prefix provides a means to specify an environment variable
   or some other prefix to the parent element.

Examples

   See any one of the parent elements for an example.

Element: <reference>

Syntax

<!ELEMENT reference      (#PCDATA)>

   This element occurs in : [403]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 : [404]Element : <alfs> | [405]Element: <stage>

Description

   The element remove is one of the top-level operation elements. It
   allows you to remove a file or directory. The content of the element
   contains the name of the file.

Note

   Not all of the rm options are in every implementation. Refer to the
   documentation for your implementation to determine what options are
   available.

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 : [406]Element: <search_replace>

Description

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

Examples

   Refer to [407]Element: <search_replace> for an example.

Element: <requires>

Syntax

<!ELEMENT requires       (name, version*)>

   This element occurs in : [408]Element: <packageinfo>

   See also : [409]Element: <name> | [410]Element: <version>

Description

   The element requires denotes a dependency between two packages. The
   package containing 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

   Refer to [411]Element: <packageinfo> for an example.

Element: <root>

Syntax

<!ELEMENT root           (#PCDATA)>

   This element occurs in : [412]Element: <stageinfo>

Description

   The element root allow you 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 : [413]Element : <alfs> | [414]Element: <stage>

   See also : [415]Element: <file> | [416]Element: <find> | [417]Element:
   <replace>

Description

   The element search_replace is one of the top-level 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.

   The attribute base specifies the directory in which the file
   replacement occurs. See [418]Element : <base>.

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 : [419]Element : <copy> | [420]Element: <move>

Description

   The element source is used to specify the name of the source in the
   parent element.

Examples

   See any one of the parent elements for an example.

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 : [421]Element : <alfs> | [422]Element: <stage>

   See also : [423]Element : <alfs> | [424]Element : <configure> |
   [425]Element : <copy> | [426]Element: <download> | [427]Element:
   <execute> | [428]Element: <link> | [429]Element: <make>> |
   [430]Element: <mkdir> | [431]Element: <move> | [432]Element:
   <ownership> | [433]Element: <package> | [434]Element: <patch> |
   [435]Element: <permissions> | [436]Element: <remove> | [437]Element:
   <search_replace> | [438]Element: <stageinfo> | [439]Element:
   <textdump> | [440]Element: <unpack>

Description

   The element stage is one of the top-level operation elements. It
   allows you 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 : [441]Element: <stage>

   See also : [442]Element: <root> | [443]Element : <base> |
   [444]Element: <environment> | [445]Element: <user>

Description

   The element stageinfo allows you to specify several contexts of
   information used to process the commands of the stage to which the
   stageinfo belongs.

   The base sub-element specifies a base directory that will be used by
   all the commands of the stage, unless the command redefines the base
   locally. See [446]Element : <base>.

   The user sub-element specifies a user name that will be used as the
   effective user ID of the current process for all the commands of the
   stage. See [447]Element: <user>.

   The root sub-element specifies a directory name in which the commands
   of the stage will be performed (using a chroot command). See
   [448]Element: <root>.

   The environment sub-element allow you to specify an environment
   variable that will be added to the current environment when processing
   the commands of the stage. See [449]Element: <environment>.

Examples

<stage name="Install gzip">

        <stageinfo>
                <root>/mnt/lfs</root>
                <user>lfs</user>
                <environment>PATH=/bin:/sbin</environment>
                <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 Executing configure
su - lfs
export PATH=/bin:/sbin
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
su - lfs
export PATH=/bin:/sbin
cd /usr/src/gzip.1.2.4a
make

echo Executing make
su - lfs
export PATH=/bin:/sbin
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage

Element: <target>

Syntax

<!ELEMENT target         (#PCDATA)>

   This element occurs in : [450]Element: <link>

Description

   The element target describes a target of a link operation.

Examples

   Refer to [451]Element: <link> for an example.

Element: <textdump>

Syntax

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

   This element occurs in : [452]Element : <alfs> | [453]Element: <stage>

   See also : [454]Element: <file> | [455]Element : <content>

Description

   The element textdump is one of the top-level operation elements. It
   allows you to create a text file containing specified text.

   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 you to specify the directory in which the
   file creation will be perforemd. See [456]Element : <base>.

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

Example #1

<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

Example #2

<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 : [457]Element : <alfs> | [458]Element: <stage>

   See also : [459]Element : <archive> | [460]Element: <destination> |
   [461]Element: <digest> | [462]Element: <reference>

Description

   The element unpack is one of the top-level operation elements. It is
   used to unpack an archive into a destination directory

   The sub-element reference gives the URL of the archive; it is only
   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 gives the name of the directory in which the
   archive is unpacked.

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 : [463]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

   Refer to [464]Element: <download> for an example.

   There is no equivalent Bash script example for this element.

Element: <user>

Syntax

<!ELEMENT user           (#PCDATA)>

   This element occurs in : [465]Element: <stageinfo>

   See also : [466]Element: <ownership>

Description

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

Examples

   Refer to [467]Element: <stageinfo> for an example.

Element: <utilizes>

Syntax

<!ELEMENT utilizes       (name, version*)>

   This element occurs in : [468]Element: <packageinfo>

   See also : [469]Element: <name> | [470]Element: <version>

Description

   The element utilizes indicates that the package containing 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 should be used).

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

Note

   To work properly, then element name must be defined in the same
   profile.

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>

   There is no equivalent Bash script example for this element.

Element: <variable>

Syntax

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

   This element occurs in : [471]Element: <environment>

Description

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

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

   The value of the variable is given by the textual content 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

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 : [472]Element: <package> | [473]Element:
   <requires> | [474]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/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2440721
   2. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface
   3. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface
   4. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-changelog
   5. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-audience
   6. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-contactinfo
   7. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2510811
   8. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2512206
   9. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2512230
  10. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2512264
  11. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-acknowledgements
  12. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-conventions
  13. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#alfs_dtd
  14. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#alfs_dtd-intro
  15. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#xml_dtd-syntax
  16. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2510181
  17. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2513906
  18. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2514001
  19. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2514070
  20. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2514177
  21. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2514503
  22. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2514748
  23. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
  24. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2513666
  25. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2515929
  26. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516033
  27. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_archive
  28. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2514927
  29. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2514949
  30. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2515611
  31. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
  32. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2515569
  33. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516615
  34. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516634
  35. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
  36. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2515009
  37. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2515370
  38. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516411
  39. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516453
  40. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516497
  41. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516543
  42. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_content
  43. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516363
  44. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516126
  45. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517663
  46. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
  47. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516323
  48. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517299
  49. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517389
  50. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
  51. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517610
  52. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517199
  53. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517216
  54. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
  55. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516728
  56. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517074
  57. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517092
  58. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517130
  59. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_digest
  60. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516907
  61. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2516938
  62. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517006
  63. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
  64. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517784
  65. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518475
  66. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518562
  67. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_environment
  68. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518154
  69. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518226
  70. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518257
  71. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
  72. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517922
  73. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519098
  74. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2517991
  75. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518025
  76. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_file
  77. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518755
  78. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519021
  79. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519055
  80. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_find
  81. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518887
  82. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518910
  83. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2518965
  84. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_include
  85. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519191
  86. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519217
  87. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519884
  88. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_item
  89. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519794
  90. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519816
  91. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2520050
  92. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
  93. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519930
  94. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2520016
  95. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2520870
  96. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_list
  97. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519692
  98. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519466
  99. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2520545
 100. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 101. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2520772
 102. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519609
 103. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2519670
 104. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521480
 105. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 106. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2520114
 107. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2520469
 108. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521274
 109. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 110. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521209
 111. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2520216
 112. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522284
 113. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 114. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521156
 115. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521957
 116. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521974
 117. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 118. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522136
 119. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522884
 120. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522901
 121. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 122. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521111
 123. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521091
 124. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522611
 125. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522673
 126. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 127. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522468
 128. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521838
 129. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521894
 130. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 131. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521667
 132. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2521751
 133. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523548
 134. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_para
 135. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523791
 136. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523722
 137. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523737
 138. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 139. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524356
 140. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523918
 141. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523136
 142. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 143. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524319
 144. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523336
 145. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523396
 146. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 147. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523279
 148. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523216
 149. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525132
 150. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 151. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524172
 152. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523942
 153. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2523959
 154. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_reference
 155. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524038
 156. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524061
 157. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525021
 158. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_remove
 159. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524823
 160. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524851
 161. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524915
 162. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_replace
 163. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524771
 164. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524432
 165. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524449
 166. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_requires
 167. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524730
 168. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524564
 169. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525670
 170. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_root
 171. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524679
 172. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524702
 173. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526000
 174. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 175. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525939
 176. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525712
 177. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525490
 178. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_source
 179. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525882
 180. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525910
 181. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525406
 182. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 183. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525214
 184. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525313
 185. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525344
 186. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 187. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526998
 188. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526410
 189. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526508
 190. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_target
 191. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526353
 192. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527151
 193. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527168
 194. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 195. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527244
 196. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528242
 197. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528315
 198. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528361
 199. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 200. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526285
 201. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527977
 202. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528040
 203. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_url
 204. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527917
 205. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527384
 206. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527407
 207. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_user
 208. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527772
 209. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527843
 210. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527861
 211. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_utilizes
 212. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527666
 213. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527500
 214. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528922
 215. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_variable
 216. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528954
 217. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528981
 218. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529061
 219. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_version
 220. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528557
 221. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529453
 222. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529510
 223. mailto:alfs-discuss@linuxfromscratch.org
 224. http://www.linuxfromscratch.org/mailman/listinfo/alfs-discuss
 225. mailto:alfs-log@linuxfromscratch.org
 226. http://www.linuxfromscratch.org/mailman/listinfo/alfs-log
 227. news:news.linuxfromscratch.org
 228. http://www.linuxfromscratch.org/
 229. http://www.linuxfromscratch.org/alfs
 230. mailto:jwrober@linuxfromscratch.org
 231. mailto:vassili@linuxfromscratch.org
 232. mailto:gerard@linuxfromscratch.org
 233. mailto:jwrober@linuxfromscratch.org
 234. http://www.linuxfromscratch.org/alfs
 235. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 236. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 237. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 238. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 239. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 240. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 241. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 242. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 243. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 244. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 245. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 246. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 247. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 248. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 249. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 250. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 251. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 252. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 253. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 254. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 255. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 256. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 257. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 258. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_remove
 259. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 260. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 261. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 262. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 263. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_include
 264. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 265. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 266. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 267. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 268. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 269. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 270. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 271. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 272. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 273. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 274. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 275. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 276. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 277. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 278. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 279. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 280. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 281. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 282. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 283. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 284. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 285. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 286. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 287. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 288. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 289. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 290. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_source
 291. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
 292. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 293. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 294. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_para
 295. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_list
 296. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 297. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 298. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 299. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 300. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 301. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 302. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 303. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_reference
 304. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 305. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 306. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_file
 307. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_url
 308. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
 309. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_digest
 310. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_digest
 311. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 312. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_variable
 313. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 314. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 315. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 316. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 317. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 318. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 319. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 320. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 321. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 322. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 323. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 324. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 325. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_list
 326. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 327. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 328. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 329. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 330. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_target
 331. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 332. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 333. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 334. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_item
 335. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 336. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 337. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 338. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 339. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 340. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 341. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 342. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 343. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 344. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 345. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 346. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 347. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 348. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 349. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 350. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 351. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_source
 352. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
 353. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 354. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 355. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 356. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 357. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 358. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_requires
 359. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_utilizes
 360. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 361. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 362. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_variable
 363. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 364. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 365. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 366. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 367. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 368. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 369. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 370. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 371. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 372. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 373. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 374. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_user
 375. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 376. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 377. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 378. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 379. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 380. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_version
 381. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 382. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 383. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_requires
 384. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_utilizes
 385. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 386. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 387. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 388. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 389. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 390. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 391. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 392. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 393. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 394. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 395. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 396. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 397. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 398. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 399. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 400. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 401. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 402. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 403. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 404. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 405. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 406. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 407. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 408. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 409. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 410. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_version
 411. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 412. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 413. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 414. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 415. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_file
 416. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_find
 417. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_replace
 418. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 419. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 420. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 421. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 422. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 423. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 424. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 425. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 426. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 427. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 428. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 429. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 430. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 431. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 432. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 433. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 434. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 435. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 436. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_remove
 437. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 438. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 439. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 440. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 441. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 442. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_root
 443. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 444. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_environment
 445. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_user
 446. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 447. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_user
 448. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_root
 449. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_environment
 450. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 451. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 452. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 453. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 454. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_file
 455. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_content
 456. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 457. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 458. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 459. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_archive
 460. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
 461. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_digest
 462. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_reference
 463. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 464. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 465. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 466. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 467. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 468. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 469. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 470. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_version
 471. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_environment
 472. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 473. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_requires
 474. file://localhost/home/jwrober/tmp/alfssyntaxdocxml/ALFS/docs/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_utilizes
