yum-software-management yum-software-management-en.xml,1.12,1.13

Stuart Ellis (elliss) fedora-docs-commits at redhat.com
Mon Jul 18 21:39:31 UTC 2005


Author: elliss

Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18638

Modified Files:
	yum-software-management-en.xml 
Log Message:

- Removed repository creation/managment material, so that this document focuses on the use of yum itself.
- More style fixes.
- Moved localinstall and proxy server sections to the end, since they aren't standard usages.



Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- yum-software-management-en.xml	18 Jul 2005 19:25:35 -0000	1.12
+++ yum-software-management-en.xml	18 Jul 2005 21:39:27 -0000	1.13
@@ -91,14 +91,6 @@
       </para>
 
       <para>
-        If you have several &FED; systems on a network you may benefit
-        from setting up their own software repositories to manage the
-        process of installation and updates. Refer to
-        <xref linkend="sn-managing-repositories"/> for the details of
-        maintaining your own repositories.
-      </para>
-
-      <para>
         Most of the examples in this document use the package
         <filename>tsclient</filename>, which is included with &FC;. The
         <filename>tsclient</filename> package provides an application
@@ -265,9 +257,8 @@
       <para>
         You may also manage related packages as sets by using the
         <firstterm>package groups</firstterm> provided by the &FED;
-        repositories. Third-party repositories may add packages to these
-        groups, or provide packages in additional groups where
-        necessary.
+        repositories. Some third-party repositories add packages to
+        these groups, or provide their packages as additional groups.
       </para>
 <!-- SE: Some repositories use groups and some don't: I've tried to put this nicely. -->
       <para>
@@ -909,110 +900,6 @@
     </section>
   </section>
 
-  <section id="sn-yum-proxy-server">
-    <title>Using <command>yum</command> with a Proxy Server</title>
-    <indexterm>
-      <primary>proxy server, with yum</primary>
-    </indexterm>
-    <indexterm>
-      <primary>yum, using a proxy server</primary>
-    </indexterm>
-    <para>
-      Repositories may be accessed through standard Web proxy servers.
-      If your system is connected to the Internet through a Web proxy
-      server, specify the details of the server in
-      <filename>/etc/yum.conf</filename>. The <command>proxy</command>
-      setting must specify the proxy server as a complete URL, including
-      the TCP port number. If your proxy server requires a username and
-      password, specify these by adding
-      <command>proxy_username</command> and
-      <command>proxy_password</command> settings.
-    </para>
-
-    <para>
-      For example, the settings below enable <command>yum</command> to
-      use the proxy server <command>mycache.mydomain.com</command>,
-      connecting to port <command>3128</command>, with the username
-      <command>yum-user</command> and the password
-      <command>qwerty</command>.
-    </para>
-
-    <example id="config-file-httpproxy">
-      <title>Configuration File Settings for Using A Proxy Server</title>
-<programlisting>
-       <![CDATA[
-         # The proxy server - proxy server:port number
-         proxy=http://mycache.mydomain.com:3128
-         # The account details for yum connections
-         proxy_username=yum-user
-         proxy_password=qwerty
-       ]]>
-      </programlisting>
-    </example>
-
-    <note>
-      <title>Global Settings</title>
-
-      <para>
-        Defining a proxy server in <filename>/etc/yum.conf</filename>
-        means that <emphasis>all</emphasis> users connect to the proxy
-        server with those details when using <command>yum</command>.
-      </para>
-    </note>
-
-    <para>
-      To enable proxy access for a specific user, add the lines in the
-      example box below to their shell profile. For the default
-      <command>bash</command> shell, the profile is the file
-      <filename>.bash_profile</filename>. The settings below enable
-      <command>yum</command> to use the proxy server
-      <command>mycache.mydomain.com</command>, connecting to port
-      <command>3128</command>.
-    </para>
-
-    <example id="profile-script-httpproxy">
-      <title>Profile Settings for Using a Proxy Server</title>
-<programlisting>
-       <![CDATA[
-         # The Web proxy server used by this account
-         http_proxy="http://mycache.mydomain.com:3128"
-         export http_proxy
-       ]]>
-      </programlisting>
-    </example>
-
-    <para>
-      If the proxy server requires a username and password then add
-      these to the URL. For example, to include the username
-      <command>yum-user</command> and the password
-      <command>qwerty</command>:
-    </para>
-
-    <example id="profile-script-httpproxy-withpassword">
-      <title>Profile Settings for a Secured Proxy Server</title>
-<programlisting>
-       <![CDATA[
-         # The Web proxy server, with the username and password for this account
-         http_proxy="http://yum-user:qwerty@mycache.mydomain.com:3128"
-         export http_proxy
-       ]]>
-      </programlisting>
-    </example>
-
-    <note>
-      <title><command>http_proxy</command> Variable with Other Utilities</title>
-
-      <para>
-        The <command>http_proxy</command> variable is also used by
-        <command>curl</command> and other utilities. Although
-        <command>yum</command> itself may use
-        <command>http_proxy</command> in either upper-case or
-        lower-case, <command>curl</command> requires the name of the
-        variable to be in lower-case.
-      </para>
-    </note>
-  </section>
-
   <section id="sn-using-repositories">
     <title>Using Other Software Repositories</title>
     <indexterm>
@@ -1025,9 +912,9 @@
       <primary>searching for repositories</primary>
     </indexterm>
     <para>
-      &FC; automatically uses the &FED; repositories. These include
-      &FEX;, the default source of packages for software that is not
-      included with &FC;.
+      &FED; systems automatically use the &FP; repositories. These
+      include &FEX;, the default source of packages for software that is
+      not included with &FC;.
     </para>
 
     <note>
@@ -1044,8 +931,8 @@
     </note>
 
     <para>
-      If the &FED; project does not provide packages for a specific
-      piece of software, the manufacturer of the software may provide or
+      If the &FP; does not provide packages for a specific piece of
+      software, the manufacturer of the software may provide or
       recommend a separate repository. Members of the community also
       maintain repositories to provide packages for &FED; systems.
       Third-party repositories provide information on their Websites.
@@ -1100,10 +987,10 @@
         <title>Repositories and <application>up2date</application> Channels</title>
 
         <para>
-          On &FC; &FCLOCALVER; systems <command>yum</command>
+          On &FED; &FCLOCALVER; systems <command>yum</command>
           repositories are automatically used as
           <application>up2date</application> channels. Repositories must
-          be separately configured as channels on &FC; 3 and earlier
+          be separately configured as channels on &FED; 3 and earlier
           systems.
         </para>
       </note>
@@ -1143,7 +1030,7 @@
 
         <para>
           The <application>up2date</application> utility automatically
-          uses the public key for &FC; packages. It does not add the
+          uses the public key for &FED; packages. It does not add the
           public key to the keyring that is used by both
           <command>yum</command> and the <command>rpm</command> utility.
         </para>
@@ -1167,28 +1054,27 @@
 
       <para>
         Before attempting to use a repository, read the Website for
-        information on package compatibility. . Repositories often
-        provide packages that are specifically intended for use with
-        packages that are supplied by other repositories. In some cases
-        separate third-party repository providers may each offer
-        different versions of the same software, preventing those
-        repositories from being safely used together by your &FC;
-        system.
+        information on package compatibility. Repositories often provide
+        packages that are specifically intended for use with packages
+        that are supplied by other repositories. In some cases separate
+        third-party repository providers may each offer different
+        versions of the same software, preventing those repositories
+        from being safely used together by your &FED; system.
       </para>
 
       <para>
-        Packages that have been made for one version of &FC; are usually
-        not compatible with other versions of &FC;. The Website of the
-        provider should specifically state which versions of &FC; they
-        support.
+        Packages that have been made for one version of &FED; are
+        usually not compatible with other versions of &FED;. The Website
+        of the provider should specifically state which versions of
+        &FED; they support.
       </para>
       <tip>
         <title>Old Versions of <command>yum</command> and Current Repositories</title>
         <para>
           The data format for repository indexes changed with version
           2.11 of <command>yum</command>. This was the version supplied
-          with &FC; 3. Repository providers should specify the versions
-          of &FC; that they support. To confirm that an unlabeled
+          with &FED; 3. Repository providers should specify the versions
+          of &FED; that they support. To confirm that an unlabeled
           repository is compatible with current versions of
           <command>yum</command>, check that it has a sub-directory
           called <filename>repo-data/</filename>.
@@ -1197,56 +1083,6 @@
     </section>
   </section>
 
-  <section id="sn-yum-installing-frompackage">
-    <title>Manually Installing Software</title>
-    <indexterm>
-      <primary>installing software with yum (from a package)</primary>
-    </indexterm>
-    <indexterm>
-      <primary>software, installing from a package</primary>
-    </indexterm>
-    <para>
-      Use repositories and the standard <command>yum</command> commands
-      to install new software, unless the software is only available as
-      a package. In these cases, use the <option>localinstall</option>
-      option to install the software from the package file without
-      connecting to any repository.
-    </para>
-
-    <important>
-      <title>Public Key is Required</title>
-
-      <para>
-        You must ensure that the public key for the package source has
-        been imported before installing a package without a repository.
-        Refer to <xref linkend="sn-authorizing-package-sources"/>
-      </para>
-    </important>
-
-    <para>
-      As an example, enter this command to install the package
-      <filename>tsclient-0.132-4.i386.rpm</filename>:
-    </para>
-<screen>
-<userinput>su -c 'yum localinstall <replaceable>tsclient-0.132-4.i386.rpm</replaceable>'</userinput>
-</screen>
-    <para>
-      Enter the <systemitem class="username">root</systemitem> password
-      when prompted.
-    </para>
-
-    <important>
-      <title>Dependencies Must Be Met</title>
-
-      <para>
-        You must ensure that all of the dependencies are already
-        installed on your system, as <command>yum</command> cannot
-        download additional packages to complete the installation in
-        this mode.
-      </para>
-    </important>
-  </section>
-
   <section id="sn-yum-maintenance">
     <title>Maintaining <command>yum</command></title>
 
@@ -1255,8 +1091,8 @@
       maintenance. It is useful to disable or remove repository
       definitions that are no longer required, as each repository that
       is defined and enabled is checked for every operation. You may
-      also wish to periodically remove files relating to unwanted
-      packages, in order to save disk space.
+      also remove files relating to unwanted packages, in order to
+      recover disk space.
     </para>
 
     <section id="sn-removing-sources">
@@ -1363,371 +1199,161 @@
     </section>
   </section>
 
-  <section id="sn-managing-repositories">
-    <title>Managing <command>yum</command> Repositories</title>
-<!-- SE: This section is NOT finished. There is a case for not trying to cover repository administration at all in this document, in which this whole section can go to live in it's own tutorial. -->
+<!-- SE: The sections below are important, but only for certain situations - they do not represent the normal use of yum. Perhaps they should be explicitly marked as appendices ?  -->
+
+  <section id="sn-yum-installing-frompackage">
+    <title>Manually Installing Software</title>
+    <indexterm>
+      <primary>installing software with yum (from a package)</primary>
+    </indexterm>
+    <indexterm>
+      <primary>software, installing from a package</primary>
+    </indexterm>
     <para>
-      You may wish to create your own software repositories, or maintain
-      a copy of another repository.
+      Use repositories and the standard <command>yum</command> commands
+      to install new software, unless the software is only available as
+      a package. In these cases, use the <option>localinstall</option>
+      function to install the software from the package file. The
+      <option>localinstall</option> function does not connect to any
+      repository.
     </para>
 
-    <caution>
-      <title>Old versions of yum use a different repository utility</title>
-
-      <para>
-        These procedures create repositories that are compatible with
-        version 2.11 of <command>yum</command> and above. You must use
-        the <command>yum-arch</command> utility that was included with
-        <command>yum</command> 2.10 to enable repositories for older
-        versions of <command>yum</command>.
-      </para>
-    </caution>
+    <important>
+      <title>Public Key is Required</title>
 
-    <section id="sn-creating-repository">
-      <title>Creating a New Repository</title>
-      <indexterm>
-        <primary>repositories, creating</primary>
-      </indexterm>
       <para>
-        A software repository is simply a directory containing package
-        files, with a sub-directory for the package index files used by
-        <command>yum</command>. The main directory may also contain
-        other types of file without interfering with the use of the
-        repository. Do not modify the <filename>data/</filename>
-        sub-directory and the XML files within it. These are created and
-        updated with the <command>createrepo</command> utility.
+        You must ensure that the public key for the package source has
+        been imported before installing a package without a repository.
+        Refer to <xref linkend="sn-authorizing-package-sources"/>
       </para>
+    </important>
 
-      <note>
-        <title>Creating Repositories Requires an Extra Package</title>
-
-        <para>
-          You must install the <filename>createrepo</filename> package
-          from &FC; in order to be able to make repositories.
-        </para>
-      </note>
-<!-- SE: The instructions below won't work as is and need amending, since the example directory can only be accessed with root privileges by default. -->
-      <para>
-        To make a directory into a <command>yum</command> repository,
-        carry the following tasks. These instructions assume that the
-        repository is the directory
-        <filename>/var/www/repository/</filename>, and that the package
-        group index file is called <filename>groups.xml</filename>:
-        <orderedlist>
-          <listitem>
-            <para>
-              Copy the RPM packages that you are distributing into the
-              directory.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              Create a groups file, as explained in
-              <xref linkend="sn-writing-groupfiles"/>
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              Open a terminal window.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              In the terminal window type: <userinput>createrepo
-              <replaceable>/var/www/repository</replaceable></userinput>.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              In the terminal window type: <userinput>createrepo -g
-              <replaceable>/var/www/repository/groups.xml</replaceable>
-              <replaceable>/var/www/repository/</replaceable></userinput>.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              In the terminal window type: <userinput>chmod a+x
-              <replaceable>/var/www/repository/repodata/</replaceable></userinput>.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              Ensure that the directory is available with your chosen
-              network protocols (HTTP, FTP, or NFS).
-            </para>
-          </listitem>
-        </orderedlist>
-      </para>
+    <para>
+      As an example, enter this command to install the package
+      <filename>tsclient-0.132-4.i386.rpm</filename>:
+    </para>
+<screen>
+<userinput>su -c 'yum localinstall <replaceable>tsclient-0.132-4.i386.rpm</replaceable>'</userinput>
+</screen>
+    <para>
+      Enter the <systemitem class="username">root</systemitem> password
+      when prompted.
+    </para>
 
-      <para>
-        The repository is now ready for use.
-      </para>
+    <important>
+      <title>Dependencies Must Be Met</title>
 
       <para>
-        Create a definition file for this new repository. If you are
-        distributing packages that you have created yourself then you
-        also need to make the GPG public key for your signature
-        available, so that others are able to verify the packages. The
-        simplest way to make these files available is to put the public
-        key and repository definition files on the same Website or FTP
-        site as the repository.
+        You must ensure that all of the dependencies are already
+        installed on your system, as <command>yum</command> cannot
+        download additional packages to complete the installation when
+        performing a <option>localinstall</option> operation.
       </para>
+    </important>
+  </section>
 
-      <para>
-        Creating a definition file is described in
-        <xref
-	linkend="sn-writing-repodefs"/>. Packaging building is
-        beyond the scope of this document.
-      </para>
-      <tip>
-        <title>Repositories and Management Utilities</title>
-        <para>
-          The <command>createrepo</command> utility makes no changes to
-          the directory other than adding a
-          <filename>repo-data/</filename> sub-directory. Adding index
-          files for other utilities does not interfere with
-          <command>yum</command>.
-        </para>
-      </tip>
-    </section>
+  <section id="sn-yum-proxy-server">
+    <title>Using <command>yum</command> with a Proxy Server</title>
+    <indexterm>
+      <primary>proxy server, with yum</primary>
+    </indexterm>
+    <indexterm>
+      <primary>yum, using a proxy server</primary>
+    </indexterm>
+    <para>
+      Repositories may be accessed through standard Web proxy servers.
+      If your system is connected to the Internet through a Web proxy
+      server, specify the details of the server in
+      <filename>/etc/yum.conf</filename>. The <command>proxy</command>
+      setting must specify the proxy server as a complete URL, including
+      the TCP port number. If your proxy server requires a username and
+      password, specify these by adding
+      <command>proxy_username</command> and
+      <command>proxy_password</command> settings.
+    </para>
 
-    <section id="sn-writing-groupfiles">
-      <title>Package Group Index Files</title>
-<!-- SE: This section is NOT finished. -->
-      <indexterm>
-        <primary>package group index files, creating</primary>
-      </indexterm>
-      <indexterm>
-        <primary>package group index files, editing</primary>
-      </indexterm>
-      <para>
-        Create and edit package group files with a text editor.
-        Definition files are XML with a standard format:
-      </para>
+    <para>
+      For example, the settings below enable <command>yum</command> to
+      use the proxy server <command>mycache.mydomain.com</command>,
+      connecting to port <command>3128</command>, with the username
+      <command>yum-user</command> and the password
+      <command>qwerty</command>.
+    </para>
 
-      <example id="yum-groupsfile-format">
-        <title>Format of <command>yum</command> Group Index Files</title>
+    <example id="config-file-httpproxy">
+      <title>Configuration File Settings for Using A Proxy Server</title>
 <programlisting>
-      <![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE comps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN" "comps.dtd">
-<comps>
-  <group>
-    <id>group-id</id>
-    <name>Group Name</name>
-    <description>Descriptive Text.</description>
-    <default>true</default> or <default>false</default>
-    <uservisible>true</uservisible> or <uservisible>false</uservisible>
-    <grouplist>
-      <groupreq>group-name</groupreq>
-    </grouplist>
-    <packagelist>
-      <packagereq type="default">package-name</packagereq> or <packagereq type="optional">package-name</packagereq>
-    </packagelist>
-  </group>
-      <grouphierarchy>
-        <category>
-          <name>Category Name</name>
-          <subcategories>
-            <subcategory>Name of Member Group</subcategory>
-          </subcategories>
-        </category>
-      </grouphierarchy>
-</comps>
-      ]]>
-    </programlisting>
-      </example>
-
-      <para>
-        The <command>id</command> and <command>name</command> that
-        identify each group must either match those of a &FED; package
-        group, or be unique. If the group matches a &FED; package group
-        then systems using the repository add the the listed packages to
-        that group when carrying out <command>yum</command> operations.
-      </para>
-<!-- SE: The explanations of the XML tags need completion. The only other documentation I've found so far that actually defines the "comps" XML format is three years old, and written for RH8. Joy ! -->
-      <para>
-        The example group file shown below defines the package groups
-        <filename>Base</filename> and <filename>Site Custom Application
-        Packages</filename>. The <filename>Base</filename> package group
-        adds extra mandatory packages to the &FED; package group for the
-        systems using the repository. <filename>Site Custom Application
-        Packages</filename> provides three packages.
-      </para>
+       <![CDATA[
+         # The proxy server - proxy server:port number
+         proxy=http://mycache.mydomain.com:3128
+         # The account details for yum connections
+         proxy_username=yum-user
+         proxy_password=qwerty
+       ]]>
+      </programlisting>
+    </example>
 
-      <example id="yum-groupsfile-example">
-        <title>Example <command>yum</command> Group Index File</title>
-<programlisting>
-      <![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE comps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN" "comps.dtd">
-<comps>
-  <group>
-    <id>base</id>
-    <name>Base</name>
-    <description>Additional packages for the Fedora Base package group.</description>
-    <default>true</default>
-    <uservisible>true</uservisible>
-    <packagelist>
-      <packagereq type="default">my-customadminpackage</packagereq>
-      <packagereq type="default">my-othercustomadminpackage</packagereq>
-  </group>
-  <group>
-    <id>site-apps</id>
-    <name>Site Custom Application Packages</name>
-    <description>Custom group for the site-specific applications.</description>
-    <default>false</default>
-    <uservisible>true</uservisible>
-    <grouplist>
-      <groupreq>base</groupreq>
-    </grouplist>
-    <packagelist>
-      <packagereq type="default">my-customapplication</packagereq>
-      <packagereq type="optional">my-othercustomapplication</packagereq>
-      <packagereq type="optional">my-optionalcustomapplication</packagereq>
-  </group>
-      <grouphierarchy>
-        <category>
-          <name>Site Custom Packages</name>
-          <subcategories>
-            <subcategory>Site Custom Application Packages</subcategory>
-          </subcategories>
-        </category>
-      </grouphierarchy>
-</comps>
-      ]]>
-    </programlisting>
-      </example>
-    </section>
+    <note>
+      <title>Global Settings</title>
 
-    <section id="sn-writing-repodefs">
-      <title>Repository Definition Files</title>
-      <indexterm>
-        <primary>repository definition files, creating</primary>
-      </indexterm>
-      <indexterm>
-        <primary>repository definition files, editing</primary>
-      </indexterm>
       <para>
-        Create and edit repository definition files with a text editor.
-        Definition files are plain-text with a standard format:
+        Defining a proxy server in <filename>/etc/yum.conf</filename>
+        means that <emphasis>all</emphasis> users connect to the proxy
+        server with those details when using <command>yum</command>.
       </para>
+    </note>
 
-      <example id="yum-repo-format">
-        <title>Format of <command>yum</command> Repository Definition Files</title>
-<programlisting>
-      <![CDATA[
-       [serverid]
-       name=Some longer name and description for this repository
-       baseurl=url://path/to/repository-copy-1/
-               url://path/to/repository-copy-2/
-       enable=(0 to disable this file, or 1 to enable it)
-       gpgcheck=(0 to disable checking signatures of packages from this repository, or 1 to enable checking)
-       gpgkey=url://path/to/gpg-key-file
-      ]]>
-    </programlisting>
-      </example>
-
-      <para>
-        The <command>baseurl</command> must specify the complete URL for
-        the <systemitem class="username">root</systemitem> directory of
-        the repository, including the <command>http://</command>,
-        <command>https://</command> or <command>ftp://</command> prefix.
-        You may also specify a directory on your system, by using the
-        prefix <command>file://</command> in the
-        <command>baseurl</command>.
-      </para>
-      <tip>
-        <title>Logging in to Protected Repositories</title>
-        <para>
-          To use a password-protected repository, include the correct
-          username and password in the <command>baseurl</command>. For
-          example,
-          <wordasword>ftp://user:password@myrepository.com/$releasever/mypackages/</wordasword>.
-        </para>
-      </tip>
-      <para>
-        If possible, list more than one directory or server that holds a
-        copy of the repository. This enables <command>yum</command> to
-        use another repository if the first is unavailable. By default,
-        <command>yum</command> randomly selects repositories from the
-        <command>baseurl</command> list. To force <command>yum</command>
-        to use them in sequence, add the option
-        <command>failovermethod=priority</command>.
-      </para>
+    <para>
+      To enable proxy access for a specific user, add the lines in the
+      example box below to their shell profile. For the default
+      <command>bash</command> shell, the profile is the file
+      <filename>.bash_profile</filename>. The settings below enable
+      <command>yum</command> to use the proxy server
+      <command>mycache.mydomain.com</command>, connecting to port
+      <command>3128</command>.
+    </para>
 
-      <para>
-        Write the URL with variables, such as
-        <command>$releasever</command>, rather than specifying fixed
-        values for these attributes. Using variables enables the same
-        definition to function when your system is upgraded to a later
-        version, or if the configuration is copied to another machine.
-        The available variables are listed on the <command>man</command>
-        page for <filename>yum.conf</filename>.
-      </para>
+    <example id="profile-script-httpproxy">
+      <title>Profile Settings for Using a Proxy Server</title>
+<programlisting>
+       <![CDATA[
+         # The Web proxy server used by this account
+         http_proxy="http://mycache.mydomain.com:3128"
+         export http_proxy
+       ]]>
+      </programlisting>
+    </example>
 
-      <para>
-        The definition file shown below uses all of these features. In
-        this example, copies of the repository are held in the directory
-        <filename>/srv/software/&FED;/&FCVER;/mypackages/</filename> on
-        the system itself, in the directory
-        <filename>software/&FED;/&FCVER;/mypackages/</filename> on the
-        Web server <wordasword>www.my-repository.com/</wordasword>, and
-        in the directory
-        <filename>pub/software/&FED;/&FCVER;/mypackages/</filename> on
-        the FTP server
-        <wordasword>server.another-repository.org</wordasword>. Here,
-        <command>yum</command> will access the FTP server with the
-        username <command>yum-user</command> and the password
-        <command>qwerty</command>. The <command>failovermethod</command>
-        ensures that <command>yum</command> checks the copy on the local
-        system, before trying the servers in sequence.
-      </para>
+    <para>
+      If the proxy server requires a username and password then add
+      these to the URL. For example, to include the username
+      <command>yum-user</command> and the password
+      <command>qwerty</command>:
+    </para>
 
-      <example id="yum-repo-multidir-example">
-        <title>A <command>yum</command> Repository Definition File with Failover</title>
+    <example id="profile-script-httpproxy-withpassword">
+      <title>Profile Settings for a Secured Proxy Server</title>
 <programlisting>
-      <![CDATA[
-       [MyPackages]
-       name=Some packages for Fedora $releasever
-       baseurl=file:///srv/software/fedora/$releasever/mypackages/
-               http://www.my-repository.com/software/fedora/$releasever/mypackages/
-               ftp://yum-user:qwerty@anotherserver.another-repository.org/pub/software/fedora/$releasever/mypackages/
-       failovermethod=priority
-       enable=1
-       gpgcheck=1
-       gpgkey=http://www.my-repository.com/software/fedora/keys/RPM-GPG-KEY.asc
-      ]]>
-    </programlisting>
-      </example>
-
-      <para>
-        To use a list of servers, substitute
-        <command>mirrorlist</command> for <command>baseurl</command>.
-      </para>
+       <![CDATA[
+         # The Web proxy server, with the username and password for this account
+         http_proxy="http://yum-user:qwerty@mycache.mydomain.com:3128"
+         export http_proxy
+       ]]>
+      </programlisting>
+    </example>
 
-      <para>
-        Set <command>gpgcheck=0</command> if it is necessary to disable
-        signature checking for the packages provided by this repository.
-        Avoid distributing or installing unsigned packages.
-      </para>
-    </section>
+    <note>
+      <title><command>http_proxy</command> Variable with Other Utilities</title>
 
-    <section id="sn-updating-repository">
-      <title>Updating a Repository</title>
-      <indexterm>
-        <primary>repositories, updating</primary>
-      </indexterm>
       <para>
-        Whenever a package is added, or replaced with a different
-        version, you must run <command>createrepo</command> again to
-        update the index files. If you are mirroring an existing
-        repository then add <command>createrepo</command> to your
-        synchronization scripts, even though the original copy may have
-        index files. This ensures that the indexes on your copy of the
-        site are accurate.
+        The <command>http_proxy</command> variable is also used by
+        <command>curl</command> and other utilities. Although
+        <command>yum</command> itself may use
+        <command>http_proxy</command> in either upper-case or
+        lower-case, <command>curl</command> requires the name of the
+        variable to be in lower-case.
       </para>
-    </section>
+    </note>
   </section>
 
   <index id="generated-index"></index>




More information about the Fedora-docs-commits mailing list