yum-software-management/en_US configuring-repositories.xml,1.2,1.3
Jared Smith (jsmith)
fedora-docs-commits at redhat.com
Tue Jan 22 03:00:12 UTC 2008
Author: jsmith
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27997
Modified Files:
configuring-repositories.xml
Log Message:
Run through tidy to avoid long lines
Index: configuring-repositories.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/configuring-repositories.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- configuring-repositories.xml 22 Jan 2008 02:58:02 -0000 1.2
+++ configuring-repositories.xml 22 Jan 2008 03:00:10 -0000 1.3
@@ -1,7 +1,7 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
+<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"
+[
<!-- *************** COMMON FDP entities *************** -->
<!ENTITY % FDP-ENTITIES SYSTEM "fdp-entities.ent">
@@ -9,66 +9,130 @@
]>
<section id="sn-ConfiguringRepositories">
<title>Configuring Access to Software Repositories</title>
- <para>Fedora systems automatically use the Fedora Project repositories. If the Fedora Project does not supply packages for a product, the manufacturer may provide or recommend a separate repository. Members of the community also maintain repositories to provide packages for Fedora systems. For example, <ulink url="http://www.jpackage.org/">http://www.jpackage.org/</ulink> distributes popular Java software as packages. </para>
- <para/>
+ <para>Fedora systems automatically use the Fedora Project
+ repositories. If the Fedora Project does not supply packages for a
+ product, the manufacturer may provide or recommend a separate
+ repository. Members of the community also maintain repositories to
+ provide packages for Fedora systems. For example,
+ <ulink url="http://www.jpackage.org/">
+ http://www.jpackage.org/</ulink>distributes popular Java software as
+ packages.</para>
+ <para />
<section id="sn-AddingRepository">
<title>Adding a Repository as a Package Source</title>
- <para>To add an extra repository, place a definition file in the <code>/etc/yum.repos.d/</code> directory on your system. Package providers make the definition files for their repositories available on their web sites. </para>
+ <para>To add an extra repository, place a definition file in the
+ <code>/etc/yum.repos.d/</code>directory on your system. Package
+ providers make the definition files for their repositories
+ available on their web sites.</para>
<note>
<title>Definition File Extension</title>
- <para> The names of repository definition files end with <code>.repo</code>. </para>
+ <para>The names of repository definition files end with
+ <code>.repo</code>.</para>
</note>
- <para>You must have <emphasis>root</emphasis> access to add a file to the definitions directory. To copy the definition file <code>example.repo</code>, type this command: </para>
+ <para>You must have
+ <emphasis>root</emphasis>access to add a file to the definitions
+ directory. To copy the definition file
+ <code>example.repo</code>, type this command:</para>
<para>
- <code> su -c 'cp example.repo /etc/yum.repos.d/' </code>
+ <code>su -c 'cp example.repo /etc/yum.repos.d/'</code>
</para>
- <para>At the prompt, enter the password for the <emphasis>root</emphasis> account. </para>
- <para>The configuration file for each repository should include a <code>gpgkey</code> setting. This setting specifies the location of a public key that verifies the packages provided by that repository. This public key is automatically imported the first time that you install software from the repository. If the configuration file provided does not include this setting, refer to <xref linkend="sn-ManuallyAuthorizing"/>. </para>
+ <para>At the prompt, enter the password for the
+ <emphasis>root</emphasis>account.</para>
+ <para>The configuration file for each repository should include a
+ <code>gpgkey</code>setting. This setting specifies the location of
+ a public key that verifies the packages provided by that
+ repository. This public key is automatically imported the first
+ time that you install software from the repository. If the
+ configuration file provided does not include this setting, refer to
+
+ <xref linkend="sn-ManuallyAuthorizing" />.</para>
</section>
<section id="sn-ManuallyAuthorizing">
<title>Manually Authorizing Package Sources</title>
- <para>To manually add a public key to your <code>rpm</code> keyring, use the import feature of the <code>rpm</code> utility. To import the file <code>GPG-PUB-KEY.asc</code>, type the following command: </para>
+ <para>To manually add a public key to your
+ <code>rpm</code>keyring, use the import feature of the
+ <code>rpm</code>utility. To import the file
+ <code>GPG-PUB-KEY.asc</code>, type the following command:</para>
<para>
- <code> su -c 'rpm --import GPG-PUB-KEY.asc' </code>
+ <code>su -c 'rpm --import GPG-PUB-KEY.asc'</code>
</para>
- <para>At the prompt, enter the password for the <emphasis>root</emphasis> account. </para>
- <para>You may also import public keys directly from a web site. For example, to import the file <code>GPG-PUB-KEY.asc</code> on the web site <emphasis>www.therepository.com</emphasis>, use this command: </para>
+ <para>At the prompt, enter the password for the
+ <emphasis>root</emphasis>account.</para>
+ <para>You may also import public keys directly from a web site. For
+ example, to import the file
+ <code>GPG-PUB-KEY.asc</code>on the web site
+ <emphasis>www.therepository.com</emphasis>, use this
+ command:</para>
<para>
- <code> su -c 'rpm --import http://www.therepository.com/GPG-PUB-KEY.asc' </code>
+ <code>su -c 'rpm --import
+ http://www.therepository.com/GPG-PUB-KEY.asc'</code>
</para>
- <para>At the prompt, enter the <emphasis>root</emphasis> password. </para>
+ <para>At the prompt, enter the
+ <emphasis>root</emphasis>password.</para>
<important>
- <title>Importing the Fedora Key</title>
- <para> To add the Fedora public key to the <code>rpm</code> keyring on Fedora systems, run the command <code>su -c 'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora'</code>. </para>
+ <title>Importing the Fedora Key</title>
+ <para>To add the Fedora public key to the
+ <code>rpm</code>keyring on Fedora systems, run the command
+ <code>su -c 'rpm --import
+ /usr/share/rhn/RPM-GPG-KEY-fedora'</code>.</para>
</important>
- <para/>
+ <para />
</section>
<section id="sn-UnderstandingRepositoryCompatibility">
<title>Understanding Repository Compatibility</title>
- <para>The Fedora Package Collection includes several thousands of packages which are compatible with each other. Third-party packages should be compatible with these Fedora Project packages, unless the provider specifically states otherwise. </para>
- <para>Always read the web site of the repository for information on package compatibility before you add it as a package source. Separate repository providers may offer different and incompatible versions of the same software. Third-party repositories may also provide alternative packages for software that is included in Fedora repositories. </para>
- <para>Alternative packages may contain versions of the software that function differently from the version in the Fedora Project packages. Determine the benefits and potential incompatibilities before replacing Fedora Project packages with alternative versions. </para>
+ <para>The Fedora Package Collection includes several thousands of
+ packages which are compatible with each other. Third-party packages
+ should be compatible with these Fedora Project packages, unless the
+ provider specifically states otherwise.</para>
+ <para>Always read the web site of the repository for information on
+ package compatibility before you add it as a package source.
+ Separate repository providers may offer different and incompatible
+ versions of the same software. Third-party repositories may also
+ provide alternative packages for software that is included in
+ Fedora repositories.</para>
+ <para>Alternative packages may contain versions of the software
+ that function differently from the version in the Fedora Project
+ packages. Determine the benefits and potential incompatibilities
+ before replacing Fedora Project packages with alternative
+ versions.</para>
<warning>
<title>Incompatible Repositories</title>
- <para> If you configure your system to use incompatible repositories yum operations may fail. </para>
+ <para>If you configure your system to use incompatible
+ repositories yum operations may fail.</para>
</warning>
- <para>Packages built for one version of Fedora are usually not compatible with other versions of Fedora. The web site of the provider should specifically state which versions of Fedora they support. </para>
+ <para>Packages built for one version of Fedora are usually not
+ compatible with other versions of Fedora. The web site of the
+ provider should specifically state which versions of Fedora they
+ support.</para>
<note>
<title>Old Versions of yum and Current Repositories</title>
- <para>The data format for repository indexes changed with version 2.1 of <code>yum</code>. This was the version supplied with Fedora Core 3. Repository providers should specify the versions of Fedora that they support. To confirm that an unlabeled repository is compatible with current versions of <code>yum</code>, check that it has a sub-directory called <code>repodata/</code>. </para>
+ <para>The data format for repository indexes changed with version
+ 2.1 of
+ <code>yum</code>. This was the version supplied with Fedora Core
+ 3. Repository providers should specify the versions of Fedora
+ that they support. To confirm that an unlabeled repository is
+ compatible with current versions of
+ <code>yum</code>, check that it has a sub-directory called
+ <code>repodata/</code>.</para>
</note>
- <para/>
+ <para />
</section>
<section id="sn-DisablingSources">
<title>Disabling or Removing Package Sources</title>
- <para>Set <code>enable=0</code> in a definition file to prevent <code>yum</code> from using that repository. The <code>yum</code> utility ignores any definition file with this setting. </para>
- <para>To completely remove access to a repository: </para>
+ <para>Set
+ <code>enable=0</code>in a definition file to prevent
+ <code>yum</code>from using that repository. The
+ <code>yum</code>utility ignores any definition file with this
+ setting.</para>
+ <para>To completely remove access to a repository:</para>
<orderedlist numeration="arabic">
<listitem>
- <para>Delete the relevant file from <code>/etc/yum.repos.d/</code>. </para>
+ <para>Delete the relevant file from
+ <code>/etc/yum.repos.d/</code>.</para>
</listitem>
<listitem>
- <para>Delete the cache directory from <code>/var/cache/yum/</code>. </para>
+ <para>Delete the cache directory from
+ <code>/var/cache/yum/</code>.</para>
</listitem>
</orderedlist>
</section>
More information about the docs-commits
mailing list