cvs commit: ALFS/docs/syntax_doc/alfs_dtd elem_requires.xml

jwrober at linuxfromscratch.org jwrober at linuxfromscratch.org
Sun Feb 22 19:16:53 PST 2004


jwrober     04/02/22 20:16:53

  Modified:    docs/syntax_doc/alfs_dtd elem_requires.xml
  Log:
  finished first pass across all elements
  
  Revision  Changes    Path
  1.6       +29 -33    ALFS/docs/syntax_doc/alfs_dtd/elem_requires.xml
  
  Index: elem_requires.xml
  ===================================================================
  RCS file: /home/cvsroot/ALFS/docs/syntax_doc/alfs_dtd/elem_requires.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- elem_requires.xml	4 Nov 2003 03:07:50 -0000	1.5
  +++ elem_requires.xml	23 Feb 2004 03:16:53 -0000	1.6
  @@ -6,16 +6,16 @@
   <title>Syntax</title>
   
   <synopsis>
  -<!ELEMENT requires          (name, version*)>
  +<!ELEMENT requires       (name, version*)>
   </synopsis>
   
  -<para>This element occurs in the element
  -<link linkend="elem_packageinfo">packageinfo</link>
  +<para>This element occurs in the element :  
  +<xref linkend="elem_packageinfo"/>
   </para>
   
  -<para>See also :
  -<link linkend="elem_name">name</link> and
  -<link linkend="elem_version">version</link>
  +<para>See also :  
  +<xref linkend="elem_name"/>  |  
  +<xref linkend="elem_version"/>
   </para>
   
   </sect2>
  @@ -23,12 +23,12 @@
   <sect2>
   <title>Description</title>
   
  -<para>The element <token>requires</token> denotes a dependency
  -between two packages : the package containg the <token>requires</token>
  -element depends on the package whose name is contained in the
  -<token>name</token> sub-element.</para>
  +<para>The element <filename>requires</filename> denotes a dependency
  +between two packages : the package containg the
  +<filename>requires</filename> element depends on the package whose name is
  +contained in the <filename>name</filename> sub-element.</para>
   
  -<para>The actual name is put into a <token>name</token> element
  +<para>The actual name is put into a <filename>name</filename> element
   because we might want to add a version in a future version.</para>
   
   </sect2>
  @@ -36,29 +36,26 @@
   <sect2>
   <title>Examples</title>
   
  -<programlisting>
  -    <package name="librep" version="0.16.1">
  -        <packageinfo>
  -                <requires><name>gmp</name></requires>
  -                <requires><name>gdbm</name></requires>
  -        </packageinfo>
  -
  -	<stage name="Unpacking a package.">
  -		<unpack>
  -			<archive>librep-0.16.1/librep-0.16.1.tar.gz</archive>
  -			<destination>/usr/src</destination>
  -		</unpack>
  -	</stage>
  +<userinput><screen><package name="librep" version="0.16.1">
  +	<packageinfo>
  +		<requires><name>gmp</name></requires>
  +		<requires><name>gdbm</name></requires>
  +	</packageinfo>
  +
  +	<stage name="Unpacking a package.">
  +		<unpack>
  +			<archive>librep-0.16.1/librep-0.16.1.tar.gz</archive>
  +			<destination>/usr/src</destination>
  +		</unpack>
  +	</stage>
   
  -	....
  +	......
   
  -    </package>
  -</programlisting>
  +</package></screen></userinput>
   
  -<para>The equivalent bash script is :</para>
  +<para>The equivalent bash script is :</para>
   
  -<programlisting>
  -#-----------------------------------------
  +<userinput><screen>#-----------------------------------------
   # processing package librep 0.16.1
   
   echo Generating package librep 0.16.1
  @@ -71,14 +68,13 @@
   
   echo Unpacking librep-0.16.1/librep-0.16.1.tar.gz into /usr/src
   cd /usr/src
  -tar xzvf librep-0.16.1/librep-0.16.1.tar.gz
  +<command>tar xzvf librep-0.16.1/librep-0.16.1.tar.gz</command>
   
   echo Exiting stage "Unpacking a package."
   
   ....
   
  -echo End of generating package librep 0.16.1
  -</programlisting>
  +echo End of generating package librep 0.16.1</screen></userinput>
   
   </sect2>
   
  
  
  



More information about the alfs-log mailing list