mirror-tutorial mirror-tutorial-en.xml,1.4,1.5

Author: pfrields

Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10180

Modified Files:
    mirror-tutorial-en.xml 
Log Message:
Removed references to yum-arch and replaced with createrepo; bump to 0.24

Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- mirror-tutorial-en.xml	18 Jun 2005 13:51:02 -0000	1.4
+++ mirror-tutorial-en.xml	22 Jul 2005 11:39:45 -0000	1.5
@@ -5,7 +5,7 @@
 <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
 %FEDORA-ENTITIES-EN;

-<!ENTITY BOOKID "mirror-tutorial-0.23 (2004-09-08)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "mirror-tutorial-0.24 (2005-07-22)"> <!-- change version of manual and date here -->

]>

@@ -76,6 +76,17 @@
           </para>
    </revdescription>
       </revision>
+      <revision>
+	<revnumber>0.24</revnumber>
+	<date>2005-07-22</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Removed references to <command>yum-arch</command> and replaced with
+	    <command>createrepo</command>.
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </articleinfo>

@@ -1047,45 +1058,37 @@

<para>
    To set up a <command>yum</command> repository, you must write a
-	directory of header information from which the clients pull the data
-	they require. The directory is named <filename>headers</filename>. It is
-	created by using the command <command>yum-arch</command>, which is run
+	directory of header information from which the clients extract the data that
+	they require. The directory is named <filename>repodata/</filename>. It is
+	created by using the command <command>createrepo</command>, which is run
    against the directory <emphasis>under which</emphasis> you want the
-	<filename>headers</filename> directory to appear. The
-	<command>yum-arch</command> program searches recursively through that
+	<filename>repodata/</filename> directory to appear. The
+	<command>createrepo</command> program searches recursively through that
    directory and any subdirectories for RPM packages, and includes them in
    the header data.
       </para>

<screen>
-<userinput>yum-arch -l -s /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput>
+<userinput>createrepo /var/ftp/pub/linux/fedora/core/&FCVER;/i386/os</userinput>
 </screen>

<para>
-	The <command>-l</command> switch follows symbolic links. This is useful
-	in the first case below. The <command>-s</command> switch includes SRPMS
-	(source RPM packages) in the header list. The command above creates the
-	<command>yum</command> header cache in the directory
+	The command above creates the <command>yum</command> header cache in the directory
    <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/headers</filename>. 
-	Typically <command>yum-arch</command> is run against at least the
+	Typically <command>createrepo</command> is run against at least the
    following locations:
       </para>
       <itemizedlist>
    <listitem>
      <para>
        The stock distribution; for example,
-	    <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/</filename>. 
-	    Use the <command>-l</command> and <command>-s</command> options to
-	    follow the linked directory <filename>SRPMS</filename> and include
-	    the source packages therein.
+	    <filename>/var/ftp/pub/linux/fedora/core/&FCVER;/i386/os/</filename>.
      </para>
    </listitem>
    <listitem>
      <para>
        Official updates to the distribution; for example,
-	    <filename>/var/ftp/pub/linux/fedora/core/updates/&FCVER;/</filename>. 
-	    Once again use <command>-l</command> and/or <command>-s</command> if
-	    appropriate.
+	    <filename>/var/ftp/pub/linux/fedora/core/updates/&FCVER;/</filename>.
      </para>
    </listitem>
       </itemizedlist>
@@ -1589,7 +1592,7 @@
      Edit <filename>/etc/sysconfig/rhn/sources</filename> for the clients
      at your site to point to your repository. For any repository, point to
      the URL for the directory containing the <filename>headers</filename>
-	  folder. You created this folder using <command>yum-arch</command> in
+	  folder. You created this folder using <command>createrepo</command> in
      <xref linkend="sn-repositories"/>. You will likely have two
      repositories, one for the stock distribution and one for updates.
      Examples are shown below; you may wish to point to an internal address
@@ -1631,3 +1634,9 @@
   </index>

</article>
+
+<!--
+Local variables:
+mode: xml
+End:
+-->