commit 895b48d96be79a79068954354570e5d8a0744a6d
Author: fnadge <fnadge(a)redhat.com>
Date: Mon Jun 21 13:22:52 2010 +0200
indexed
en-US/PackageKit.xml | 12 +++-
en-US/Yum.xml | 141 ++++++++++++++++++++++++++++++++------------------
2 files changed, 100 insertions(+), 53 deletions(-)
---
diff --git a/en-US/PackageKit.xml b/en-US/PackageKit.xml
index bf699b6..3708358 100644
--- a/en-US/PackageKit.xml
+++ b/en-US/PackageKit.xml
@@ -1,17 +1,23 @@
<?xml version='1.0'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<chapter
- id="ch-PackageKit">
+<chapter id="ch-PackageKit">
<title>PackageKit</title>
<indexterm>
<primary>PackageKit</primary>
</indexterm>
- <para>Red Hat provides <application>PackageKit</application> for
viewing, managing, updating, installing and uninstalling packages compatible with your
system. <application>PackageKit</application> consists of several graphical
interfaces that can be opened from the GNOME panel menu, or from the Notification Area
when <application>PackageKit</application> alerts you that updates are
available. For more information on <application>PackageKit's</application>
architecture and available front ends, refer to <xref
+ <para>Red Hat provides <application>PackageKit</application> for
viewing, managing, updating, installing and uninstalling packages<indexterm>
+ <primary>Packages</primary><secondary>viewing packages with
PackageKit</secondary></indexterm>
+ <indexterm><primary>Packages</primary><secondary>managing
packages with PackageKit</secondary></indexterm>
+ <indexterm><primary>Packages</primary><secondary>updating
packages with PackageKit</secondary></indexterm>
+ <indexterm><primary>Packages</primary><secondary>installing
packages with PackageKit</secondary></indexterm>
+ <indexterm><primary>Packages</primary><secondary>uninstalling
packages with PackageKit</secondary></indexterm>
+ compatible with your system. <application>PackageKit</application>
consists of several graphical interfaces that can be opened from the GNOME panel menu, or
from the Notification Area when <application>PackageKit</application> alerts
you that updates are available. For more information on
<application>PackageKit's</application> architecture and available front
ends, refer to <xref
linkend="sec-PackageKit_Architecture"/>.</para>
<section
id="sec-Updating_Packages_with_Software_Update">
<title>Updating Packages with Software Update</title>
+
<para>
<application>PackageKit</application> displays a starburst icon in the
Notification Area whenever updates are available to be installed on your
system.</para>
<mediaobject>
diff --git a/en-US/Yum.xml b/en-US/Yum.xml
index e87d8d4..11266a5 100644
--- a/en-US/Yum.xml
+++ b/en-US/Yum.xml
@@ -1,23 +1,16 @@
<?xml version='1.0'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<chapter
- id="ch-yum">
+
+<chapter id="ch-yum">
+
<title>Yum</title>
- <indexterm>
- <primary>Yum Package Manager</primary>
- <see>Yum</see>
- </indexterm>
- <indexterm>
- <primary>Yum</primary>
- </indexterm>
- <para>
- <application>Yum</application> is the &OSORG; package manager that is
able to query for information about packages, fetch packages from repositories, install
and uninstall packages using automatic dependency resolution, and update an entire system
to the latest available packages. <application>Yum</application> performs
automatic dependency resolution on packages you are updating, installing or removing, and
thus is able to automatically determine, fetch and install all available dependent
packages. <application>Yum</application> can be configured with new,
additional repositories, or <firstterm>package sources</firstterm>, and also
provides many plugins which enhance and extend its capabilities.
<application>Yum</application> is able to perform many of the same tasks that
<application>RPM</application> can; additionally, many of the command line
options are similar. <application>Yum</application> enables easy and simple
package management on a single machine or on group
s of them.</para>
+
+ <para><application>Yum</application> is the &OSORG; package
manager that is able to query for information about packages, fetch packages from
repositories, install and uninstall packages using automatic dependency resolution, and
update an entire system to the latest available packages.
<application>Yum</application> performs automatic dependency resolution on
packages you are updating, installing or removing, and thus is able to automatically
determine, fetch and install all available dependent packages.
<application>Yum</application> can be configured with new, additional
repositories, or <firstterm>package sources</firstterm>, and also provides
many plugins which enhance and extend its capabilities.
<application>Yum</application> is able to perform many of the same tasks that
<application>RPM</application> can; additionally, many of the command line
options are similar. <application>Yum</application> enables easy and simple
package management on a single machine or on g
roups of them.</para>
<important
id="important-Secure_Package_Management_with_GPG-Signed_Packages">
<title>Secure Package Management with GPG-Signed Packages</title>
- <para>
- <application>Yum</application> provides secure package management by
enabling GPG (Gnu Privacy Guard; also known as GnuPG) signature verification on GPG-signed
packages to be turned on for all package repositories (i.e. package sources), or for
individual repositories. When signature verification is enabled,
<application>Yum</application> will refuse to install any packages not
GPG-signed with the correct key for that repository. This means that you can trust that
the <application>RPM</application> packages you download and install on your
system are from a trusted source, such as &OSORG;, and were not modified during
transfer. Refer to <xref
+ <para><application>Yum</application> provides secure package
management by enabling GPG (Gnu Privacy Guard; also known as GnuPG) signature verification
on GPG-signed packages to be turned on for all package repositories (i.e. package
sources), or for individual repositories. When signature verification is enabled,
<application>Yum</application> will refuse to install any packages not
GPG-signed with the correct key for that repository. This means that you can trust that
the <application>RPM</application> packages you download and install on your
system are from a trusted source, such as &OSORG;, and were not modified during
transfer. Refer to <xref
linkend="sec-Configuring_Yum_and_Yum_Repositories"/> for details on
enabling signature-checking with <application>Yum</application>, or <xref
linkend="s1-check-rpm-sig"/> for information on working with and
verifying GPG-signed <application>RPM</application> packages in
general.</para>
</important>
@@ -31,6 +24,10 @@
<section
id="sec-Checking_For_Updates">
<title>Checking For Updates</title>
+ <indexterm>
+ <primary>Yum Updates</primary>
+ <secondary>checking for updates</secondary>
+ </indexterm>
<para>You can use the <command>yum check-update</command> command
to see which installed packages on your system have updates available.</para>
<note
id="note-Note_Yum_and_Superuser_Privileges">
@@ -78,7 +75,9 @@ yum.noarch 3.2.24-4.el6 rhel
<section
id="sec-Updating_Packages">
<title>Updating Packages</title>
- <para>You can choose to update a single package, multiple packages, or all
packages at once. If any dependencies of the package (or packages) you update have updates
available themselves, then they are updated too. To update a single package, enter
<command>yum update <package_name></command>:</para>
+ <indexterm significance="normal">
+ <primary>Yum Updates</primary><secondary>updating
packages</secondary></indexterm>
+ <para>You can choose to update a single package, multiple packages, or all
packages at once. If any dependencies of the package (or packages) you update have updates
available themselves, then they are updated too. To update a single
package<indexterm><primary>Yum
Updates</primary><secondary>updating a single
package</secondary></indexterm>, enter <command>yum update
<package_name></command>:</para>
<screen>
~]# <command>yum update udev</command>
Loaded plugins: presto, refresh-packagekit, rhnplugin, security
@@ -132,7 +131,7 @@ Is this ok [y/N]:
</listitem>
</orderedlist>
<bridgehead
- id="bh-Updating_All_Packages_and_Their_Dependencies">Updating All
Packages and Their Dependencies</bridgehead>
+ id="bh-Updating_All_Packages_and_Their_Dependencies">Updating All
Packages and Their Dependencies</bridgehead><indexterm><primary>Yum
Updates</primary><secondary>updating all packages and
dependencies</secondary></indexterm>
<para>To update all packages and their dependencies, simply enter
<command>yum update</command> (without any arguments):</para>
<example
id="ex-Updating_all_packages_at_once">
@@ -145,22 +144,32 @@ Is this ok [y/N]:
<section
id="sec-Updating_Security-Related_Packages">
<title>Updating Security-Related Packages</title>
- <para>Discovering which packages have security updates available and then
updating those packages quickly and easily is important.
<application>Yum</application> provides the
<application>security</application> plugin for this purpose. The
<application>security</application> plugin extends the
<command>yum</command> command with a set of highly-useful security-centric
commands, subcommands and options. Refer to <xref
+ <indexterm><primary>Yum
Updates</primary><secondary>updating security-related
packages</secondary></indexterm>
+ <indexterm><primary>Security-Related
Packages</primary><secondary>updating security-related
packages</secondary></indexterm>
+ <para>Discovering which packages have security updates available and then
updating those packages quickly and easily is important.
<application>Yum</application> provides the
<indexterm><primary><application>security</application>
plugin</primary><see>Security </see></indexterm> plugin for this
purpose. The <application>security</application> plugin extends the
<command>yum</command> command with a set of highly-useful security-centric
commands, subcommands and options. Refer to <xref
linkend="bh-security_yum-plugin-security"/> for specific
information.</para>
</section>
<section
id="sec-Preserving_Configuration_File_Changes">
<title>Preserving Configuration File Changes</title>
- <para>You will inevitably make changes to the configuration files installed
by packages as you use your &MAJOROS; system.
<application>RPM</application>, which
<application>Yum</application> uses to perform changes to the system, provides
a mechanism for ensuring their integrity. Refer to <xref
- linkend="sec-Installing_and_Upgrading"/> for details on how to
manage changes to configuration files across package upgrades.</para>
+ <indexterm><primary>Configuration File
Changes</primary></indexterm>
+ <para>You will inevitably make changes to the configuration files installed
by packages as you use your &MAJOROS; system.
<application>RPM</application>, which
<application>Yum</application> uses to perform changes to the system, provides
a mechanism for ensuring their integrity. Refer to <xref
linkend="sec-Installing_and_Upgrading"/> for details on how to manage changes
to configuration files across package upgrades.</para>
</section>
</section>
<section
id="sec-Packages_and_Package_Groups">
<title>Packages and Package Groups</title>
+ <indexterm><primary>packages</primary><secondary>packages and
package roups</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>packages and
package roups</secondary></indexterm>
<section
id="sec-Searching_Listing_and_Displaying_Package_Information">
<title>Searching, Listing and Displaying Package Information</title>
+ <indexterm><primary>packages</primary><secondary>searching
packages with Yum</secondary></indexterm>
+ <indexterm><primary>packages</primary><secondary>listing
packages with Yum</secondary></indexterm>
+ <indexterm><primary>packages</primary><secondary>displaying
packages with Yum</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>searching
packages with Yum</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>listing
packages with Yum</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>displaying
packages with Yum</secondary></indexterm>
<para>You can search all <application>RPM</application> package
names, descriptions and summaries by using the <command>yum search
<replaceable><term></replaceable> <optional><replaceable>more_terms</replaceable>
</optional>
</command> command. <command>yum</command> displays the list of
matches for each term:</para>
@@ -172,14 +181,20 @@ kdesdk.x86_64 : The KDE Software Development Kit (SDK)
Warning: No matches found for: meld
</screen>
<para>
+ <indexterm><primary>packages</primary><secondary>searching
for packages with Yum</secondary><tertiary>yum
search</tertiary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>searching for
packages with Yum</secondary><tertiary>yum
search</tertiary></indexterm>
<command>yum search</command> is useful for searching for packages
you do not know the name of, but for which you know a related term.</para>
<bridgehead
id="bh-Listing_Packages">Listing Packages</bridgehead>
<para>
- <command>yum list</command> and related commands provide information
about packages, package groups, and repositories.</para>
+ <indexterm><primary>packages</primary><secondary>listing
packages with Yum</secondary><tertiary>yum
search</tertiary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>listing
packages with Yum</secondary><tertiary>yum
list</tertiary></indexterm>
+ <command>yum list</command> and related commands provide information
about packages, package groups, and repositories.</para>
<note
id="note-Tip-Filtering_Results_with_Glob_Expressions">
<title>Tip: Filtering Results with Glob Expressions</title>
+ <indexterm><primary>packages</primary><secondary>listing
packages with Yum</secondary><tertiary> Glob
expressions</tertiary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>listing
packages with Yum</secondary><tertiary>Glob
expressions</tertiary></indexterm>
<para>All of <application>Yum</application>'s various list
commands allow you to filter the results by appending one or more <emphasis>glob
expressions</emphasis> as arguments. Glob expressions are normal strings of
characters which contain one or more of the wildcard characters
<command>*</command> (which expands to match any character multiple times) and
<command>?</command> (which expands to match any one character). Be careful to
escape both of these glob characters when passing them as arguments to a
<command>yum</command> command. If you do not, the bash shell will interpret
the glob expressions as <emphasis>pathname expansions</emphasis>, and
potentially pass all files in the current directory that match the globs to
<command>yum</command>, which is not what you want. Instead, you want to pass
the glob expressions themselves to <command>yum</command>, which you can do by
either:
<itemizedlist>
<listitem>
@@ -242,31 +257,31 @@ abrt-plugin-ticketuploader.x86_64 1.0.7-5.el6
@rhel</scr
<itemizedlist>
<listitem>
<para>
- <command>yum list all</command> — List all installed
<emphasis>and</emphasis> available packages.</para>
+ <command>yum list all</command> —
<indexterm><primary>packages</primary><secondary>listing packages
with Yum</secondary><tertiary>yum list
all</tertiary></indexterm><indexterm><primary>Yum</primary><secondary>listing
packages with Yum</secondary><tertiary>yum list
all</tertiary></indexterm>List all installed
<emphasis>and</emphasis> available packages.</para>
</listitem>
<listitem>
<para>
- <command>yum list installed</command> — List all packages
installed on your system. The rightmost column in the output lists the repository from
which the package was retrieved.</para>
+ <command>yum list installed</command> —
<indexterm><primary>packages</primary><secondary>listing packages
with Yum</secondary><tertiary>yum list
installed</tertiary></indexterm><indexterm><primary>Yum</primary><secondary>listing
packages with Yum</secondary><tertiary>yum list
installed</tertiary></indexterm>List all packages installed on your system.
The rightmost column in the output lists the repository from which the package was
retrieved.</para>
</listitem>
<listitem>
<para>
- <command>yum list available</command> — List all available
packages in all enabled repositories.</para>
+ <command>yum list available</command> —
<indexterm><primary>packages</primary><secondary>listing packages
with Yum</secondary><tertiary>yum list
available</tertiary></indexterm><indexterm><primary>Yum</primary><secondary>listing
packages with Yum</secondary><tertiary>yum list
available</tertiary></indexterm>List all available packages in all enabled
repositories.</para>
</listitem>
<listitem>
<para>
- <command>yum grouplist</command> — List all package
groups.</para>
+ <command>yum grouplist</command> —
<indexterm><primary>packages</primary><secondary>listing packages
with Yum</secondary><tertiary>yum
grouplist</tertiary></indexterm><indexterm><primary>Yum</primary><secondary>listing
packages with Yum</secondary><tertiary>yum
grouplist</tertiary></indexterm>List all package groups.</para>
</listitem>
<listitem>
<para>
- <command>yum repolist</command> — List the repository ID, name,
and number of packages it provides for each <emphasis>enabled</emphasis>
repository.</para>
+ <command>yum repolist</command> —
<indexterm><primary>packages</primary><secondary>listing packages
with Yum</secondary><tertiary>yum
repolist</tertiary></indexterm><indexterm><primary>Yum</primary><secondary>listing
packages with Yum</secondary><tertiary>yum
repolist</tertiary></indexterm>List the repository ID, name, and number of
packages it provides for each <emphasis>enabled</emphasis>
repository.</para>
</listitem>
</itemizedlist>
<bridgehead
- id="bh-Displaying_Package_Info">Displaying Package
Info</bridgehead>
+ id="bh-Displaying_Package_Info">Displaying Package
Info</bridgehead>
<para>
<command>yum info
<replaceable><package_name></replaceable> <optional><replaceable>more_names</replaceable>
</optional>
- </command> displays information about one or more packages (glob
expressions are valid here as well):</para>
+
</command><indexterm><primary>packages</primary><secondary>displaying
packages with Yum</secondary><tertiary>yum
info</tertiary></indexterm><indexterm><primary>Yum</primary><secondary>displaying
packages with Yum</secondary><tertiary>yum
info</tertiary></indexterm> displays information about one or more packages
(glob expressions are valid here as well):</para>
<screen>
~]# <command>yum info abrt</command>
Loaded plugins: presto, refresh-packagekit, rhnplugin, security
@@ -287,6 +302,8 @@ Description: abrt is a tool to help users to detect defects in
applications
: functionality.
</screen>
<para>
+ <indexterm><primary>packages</primary><secondary>displaying
packages</secondary><tertiary>yum info</tertiary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>displaying
packages</secondary><tertiary>yum info</tertiary></indexterm>
<command>yum info
<replaceable><package_name></replaceable>
</command> is similar to the <command>rpm -q --info
<replaceable><package_name></replaceable>
</command> command, but provides as additional information the ID of the
<application>Yum</application> repository the RPM package is found in (look
for the <emphasis>From repo:</emphasis> line in the output).</para>
@@ -312,9 +329,12 @@ yum-3.2.27-4.el6.noarch
<title>Installing</title>
<indexterm>
<primary>packages</primary>
- <secondary>installing</secondary>
- <tertiary>with Yum</tertiary>
- </indexterm>
+ <secondary>installing with Yum</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>Yum</primary>
+ <secondary>installing with Yum</secondary>
+ </indexterm>
<para>You can install a package and all of its non-installed dependencies by
entering:</para>
<screen>~]# <command>yum install
<replaceable><package_name></replaceable>
</command>
@@ -363,7 +383,9 @@ Filename : /usr/sbin/named
</note>
<bridgehead
id="bh-Installing_a_Package_Group">Installing a Package
Group</bridgehead>
- <para>A package group is similar to a package: it is not useful itself, but
installing one also pulls in a group of dependent packages that serve a common purpose. A
package group has a name and a groupid. The <command>yum grouplist
-v</command> command lists the names of all package groups, and, next to each of
them, their <firstterm>groupid</firstterm> in parentheses. The groupid is
always the term in the last pair of parentheses, such as
<literal>kde-desktop</literal> and
<literal>kde-software-development</literal> in this example:</para>
+
<indexterm><primary>packages</primary><secondary>installing a
package group with Yum</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>installing a
package group with Yum</secondary></indexterm>
+ <para>A package group is similar to a package: it is not useful by
itsself, but installing one pulls a group of dependent packages that serve a common
purpose. A package group has a name and a groupid. The <command>yum grouplist
-v</command> command lists the names of all package groups, and, next to each of
them, their <firstterm>groupid</firstterm> in parentheses. The groupid is
always the term in the last pair of parentheses, such as
<literal>kde-desktop</literal> and
<literal>kde-software-development</literal> in this example:</para>
<important>
<title>Not all packages used in examples may be available on
RHN</title>
<para>Some of the software packages—or package groups—queried for and
installed with <application>Yum</application> in this chapter may not be
available from Red Hat Network. Their use in examples is purely to demonstrate
<application>Yum</application>'s command usage.</para>
@@ -390,12 +412,16 @@ KDE Software Development (kde-software-development)
<section
id="sec-Removing">
<title>Removing</title>
+
<indexterm><primary>packages</primary><secondary>uninstalling
packages with Yum</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>uninstalling
packages with Yum</secondary></indexterm>
<para>
- <command>yum remove <package_name></command> uninstalls
(removes in <application>RPM</application> and
<application>Yum</application> terminology) the package, as well as any
packages that depend on it. As when you install multiple packages, you can remove several
at once by adding more package names to the command:</para>
+ <command>yum remove
<package_name></command><indexterm><primary>packages</primary><secondary>uninstalling
packages with Yum</secondary><tertiary>yum remove
package_name</tertiary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>uninstalling
packages with Yum</secondary><tertiary>yum remove
package_name</tertiary></indexterm>uninstalls (removes in
<application>RPM</application> and <application>Yum</application>
terminology) the package, as well as any packages that depend on it. As when you install
multiple packages, you can remove several at once by adding more package names to the
command:</para>
<screen>
-~]# <command>yum remove foo bar baz</command>
+ <command>yum remove foo bar baz</command>
</screen>
- <para>Similar to the <command>install</command> command, remove
can take, as arguments, package names, glob expressions, file lists or package
provides.</para>
+ <para>Similar to <command>install</command>,
<command>remove</command> can take these arguments:
<itemizedlist><listitem><para>package
names</para></listitem><listitem><para>glob
expressions</para></listitem><listitem><para>file
lists</para></listitem><listitem><para>package
provides</para></listitem></itemizedlist></para>
+
<warning
id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It">
<title>Warning: Removing a Package when Other Packages Depend On
It</title>
@@ -418,6 +444,8 @@ KDE Software Development (kde-software-development)
<important
id="important-Smart_package_group_removal">
<title>Smart package group removal</title>
+ <indexterm><primary>packages</primary><secondary>removing
package groups with Yum</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>uninstalling
package groups with Yum</secondary></indexterm>
<para>When you tell <application>yum</application> to remove a
package group, it will remove every package in that group, even if those packages are
members of other package groups or dependencies of other installed packages. However, you
can instruct <command>yum</command> to remove only those packages which are
not required by any other packages or groups by adding the
<option>groupremove_leaf_only=1</option> directive to the
<literal>[main]</literal> section of the
<filename>/etc/yum.conf</filename> configuration file. For more information on
this directive, refer to <xref
linkend="sec-Setting_main_Options"/>.</para>
</important>
@@ -426,6 +454,8 @@ KDE Software Development (kde-software-development)
<section
id="sec-Configuring_Yum_and_Yum_Repositories">
<title>Configuring Yum and Yum Repositories</title>
+ <indexterm><primary>Yum</primary><secondary>configuring
Yum and Yum repositories</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>Yum
repositories</secondary><tertiary>configuring Yum and Yum
repositories</tertiary></indexterm>
<para>This section shows you how to:</para>
<itemizedlist>
<listitem>
@@ -446,6 +476,7 @@ KDE Software Development (kde-software-development)
<section
id="sec-Setting_main_Options">
<title>Setting [main] Options</title>
+ <indexterm><primary>Yum</primary><secondary>setting [main]
options</secondary></indexterm>
<para>The <filename>/etc/yum.conf</filename> configuration file
contains exactly one <literal>[main]</literal> section. You can add many
additional options under the <literal>[main]</literal> section heading in
<filename>/etc/yum.conf</filename>. Some of the key-value pairs in the
<literal>[main]</literal> section affect how
<command>yum</command> operates; others affect how
<application>Yum</application> treats repositories. The best source of
information for all <application>Yum</application> options is in the
<literal>[main] OPTIONS</literal> and <literal>[repository]
OPTIONS</literal> sections of <command>man
yum.conf</command>.</para>
<para>Here is a sample <filename>/etc/yum.conf</filename>
configuration file:</para>
<screen>
@@ -539,6 +570,7 @@ installonly_limit=3
<section
id="sec-Setting_repository_Options">
<title>Setting [repository] Options</title>
+ <indexterm><primary>Yum</primary><secondary>setting
[repository] options</secondary></indexterm>
<para>You can define individual <application>Yum</application>
repositories by adding [<replaceable>repository</replaceable>] sections (where
<replaceable>repository</replaceable> is a unique repository ID, such as
[<replaceable>my_personal_repo</replaceable>]) to
<filename>/etc/yum.conf</filename> or to
<filename>.repo</filename> files in the
<filename>/etc/yum.repos.d/</filename>directory. All
<filename>.repo</filename> files in
<filename>/etc/yum.repos.d/</filename>are read by
<command>yum</command>; best practice is to define your repositories here
instead of in <filename>/etc/yum.conf</filename>. You can create new, custom
<filename>.repo</filename> files in this directory, add
[<replaceable>repository</replaceable>] sections to those files, and the next
time you run a <command>yum</command> command, it will take all newly-added
repositories into account.</para>
<para>Here is a (bare-minimum) example of the form a
<filename>.repo</filename> file should take:</para>
<screen>
@@ -606,48 +638,47 @@ baseurl=http://path/to/repo or ftp://path/to/repo or
file://path/to/local/repo
<section
id="sec-Using_Yum_Variables">
<title>Using Yum Variables</title>
+
<indexterm><primary>Yum</primary><secondary>variables</secondary></indexterm>
<para>You can use and reference the following variables in
<command>yum</command> commands and in all
<application>Yum</application> configuration files
(<filename>/etc/yum.conf</filename> and all
<filename>.repo</filename> files in
<filename>/etc/yum.repos.d/</filename>.</para>
<variablelist>
<varlistentry>
<term>
<envar>$releasever</envar>
- </term>
- <listitem>
- <para>You can use this variable to reference the release version of
&MAJOROS;. <application>Yum</application> obtains the value of
<envar>$releasever</envar> from the
<literal>distroverpkg=<value></literal> line in the
<filename>/etc/yum.conf</filename> configuration file. If there is no such
line in <filename>/etc/yum.conf</filename>, then
<command>yum</command> infers the correct value by deriving the version number
from the <filename>redhat-release</filename> package.</para>
+ </term>
+ <listitem><para>You can use this variable to reference the release
version of &MAJOROS;. <application>Yum</application> obtains the value of
<filename>$releasever</filename> from the
<literal>distroverpkg=<value></literal> line in the
<filename>/etc/yum.conf</filename> configuration file. If there is no such
line in <filename>/etc/yum.conf</filename>, then
<command>yum</command> infers the correct value by deriving the version number
from the <filename>redhat-release</filename> package.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<envar>$arch</envar>
- </term>
- <listitem>
- <para>You can use this variable to refer to the system's CPU
architecture as returned when calling Python's
<methodname>os.uname()</methodname> function. Valid values for
<envar>$arch</envar> include: <literal>i586</literal>,
<literal>i686</literal> and
<literal>x86_64</literal>.</para>
+ </term>
+ <listitem><para>You can use this variable to refer to the
system's CPU architecture as returned when calling Python's
<methodname>os.uname()</methodname> function. Valid values for
<envar>$arch</envar> include: <literal>i586</literal>,
<literal>i686</literal> and
<literal>x86_64</literal>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<envar>$basearch</envar>
</term>
- <listitem>
- <para>You can use <envar>$basearch</envar> to reference the
base architecture of the system. For example, i686 and i586 machines both have a base
architecture of <literal>i386</literal>, and AMD64 and Intel64 machines have a
base architecture of <literal>x86_64</literal>.</para>
+ <listitem><para>You can use <envar>$basearch</envar>
to reference the base architecture of the system. For example, i686 and i586 machines both
have a base architecture of <literal>i386</literal>, and AMD64 and Intel64
machines have a base architecture of <literal>x86_64</literal>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<envar>$YUM0-9</envar>
</term>
- <listitem>
- <para>These ten variables are each replaced with the value of any shell
environment variables with the same name. If one of these variables is referenced (in
<filename>/etc/yum.conf</filename> for example) and a shell environment
variable with the same name does not exist, then the configuration file variable is not
replaced.</para>
+ <listitem><para>These ten variables are each replaced with the
value of any shell environment variables with the same name. If one of these variables is
referenced (in <filename>/etc/yum.conf</filename> for example) and a shell
environment variable with the same name does not exist, then the configuration file
variable is not replaced.</para>
</listitem>
</varlistentry>
</variablelist>
</section>
<section
id="sec-Creating_a_Yum_Repository">
- <title>Creating a Yum Repository</title>
+ <title>Creating a Yum Repository</title>
+
<indexterm><primary>Yum</primary><secondary>repository</secondary></indexterm>
<para>To set up a <application>Yum</application> repository,
follow these steps:</para>
<procedure
id="procedure-Setting_Up_a_Yum_repository">
+
<title>Setting Up a <application>Yum</application>
repository</title>
<step>
<para>Install the <filename>createrepo</filename>
package:</para>
@@ -669,8 +700,9 @@ baseurl=http://path/to/repo or ftp://path/to/repo or
file://path/to/local/repo
<section
id="sec-Yum_Plugins">
<title>Yum Plugins</title>
+ <indexterm><primary>Yum</primary><secondary>Yum
plugins</secondary></indexterm>
<para>
- <application>Yum</application> provides plugins that extend and enhance
its operations. Certain plugins are installed by default.
<application>Yum</application> always informs you which plugins, if any, are
loaded and in effect whenever you call any <command>yum</command>
command:</para>
+ <application>Yum</application> provides plugins that extend and enhance
its operations. Certain plugins are installed by default.
<application>Yum</application> always informs you which plugins, if any, are
loaded and active whenever you call any <command>yum</command>
command:</para>
<screen>
~]# <command>yum info yum</command>
Loaded plugins: presto, refresh-packagekit, security
@@ -681,6 +713,10 @@ Loaded plugins: presto, refresh-packagekit, security
<section
id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins">
<title>Enabling, Configuring and Disabling Yum Plugins</title>
+ <indexterm><primary>Yum</primary><secondary>enabling
plugins</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>configuring
plugins</secondary></indexterm>
+ <indexterm><primary>Yum</primary><secondary>disabling
plugins</secondary></indexterm>
+
<para>To enable <application>Yum</application> plugins, ensure
that a line beginning with <command>plugins=</command> is present in the
<literal>[main]</literal> section of
<filename>/etc/yum.conf</filename>, and that its value is set to
<constant>1</constant>:</para>
<screen>
plugins=1
@@ -723,18 +759,22 @@ enabled=1
<para>Here are descriptions of a few useful
<application>Yum</application> plugins:</para>
<bridgehead
id="bh-presto_yum-presto">presto (yum-presto)</bridgehead>
+
<indexterm><primary>Yum</primary><secondary>plugins</secondary><tertiary>yum-presto</tertiary></indexterm>
<para>The <application>presto</application> plugin adds support
to <application>Yum</application> for downloading <firstterm>delta
RPM</firstterm> packages, during updates, from repositories which have
<application>presto</application> metadata enabled. Delta RPMs contain only
the differences between the version of the the package installed on the client requesting
the RPM package and the updated version in the repository. Downloading a delta RPM is much
quicker than downloading the entire updated package, and can speed up updates
considerably. Once the delta RPMs are downloaded, they must be rebuilt (the difference
applied to the currently-installed package to create the full updated package) on the
installing machine, which takes CPU time. Using delta RPMs is therefore a tradeoff between
time-to-download, which depends on the network connection, and time-to-rebuild, which is
CPU-bound. Using the <application>presto</application> plugin is recommended
for fast machine
s and systems with slower network connections, while slower machines on very fast
connections <emphasis>may</emphasis> benefit more from downloading normal RPM
packages, i.e. by disabling <application>presto</application>. The
<application>presto</application> plugin is enabled by default.</para>
- <bridgehead
-
id="bh-protect-packages_yum-plugin-protect-packages">protect-packages
(yum-plugin-protect-packages)</bridgehead>
+
+ <bridgehead
id="bh-protect-packages_yum-plugin-protect-packages">protect-packages
(yum-plugin-protect-packages)</bridgehead>
+
<indexterm><primary>Yum</primary><secondary>plugins</secondary><tertiary>yum-plugin-protect-packages</tertiary></indexterm>
<para>The <application>protect-packages</application> plugin
prevents the <filename>yum</filename> package and all packages it depends on
from being purposefully or accidentally removed. This simple scheme prevents many of the
most important packages necessary for your system to run from being removed. In addition,
you can list more packages, one per line, in the
<filename>/etc/sysconfig/protected-packages</filename> file<footnote
id="footnote-Alternative_Locations_for_protect-packages_Lists"><para>You
can also place files with the extension <filename>.list</filename> in the
<filename>/etc/sysconfig/protected-packages.d/</filename> directory (which you
should create if it does not exist), and list packages—one per line—in these files.
<application>protect-packages</application> will protect these
too.</para>
</footnote>
(which you should create if it does not exist), and
<application>protect-packages</application> will extend
protection-from-removal to those packages as well. To temporarily override package
protection, use the <option>--override-protection</option> option with an
applicable <command>yum</command> command.</para>
<bridgehead
id="bh-refresh-packagekit_PackageKit-yum-plugin">refresh-packagekit
(PackageKit-yum-plugin)</bridgehead>
- <para>This plugin updates metadata for
<application>PackageKit</application> whenever
<application>yum</application> is run. The
<application>refresh-packagkit</application> plugin is installed by
default.</para>
- <bridgehead
- id="bh-security_yum-plugin-security">security
(yum-plugin-security)</bridgehead>
+
<indexterm><primary>Yum</primary><secondary>plugins</secondary><tertiary>PackageKit-yum-plugin</tertiary></indexterm>
+ <para>This plugin updates metadata for
<application>PackageKit</application> whenever
<application>yum</application> is run. The
<application>refresh-packagkit</application> plugin is installed by
default.</para>
+
+ <bridgehead id="bh-security_yum-plugin-security">security
(yum-plugin-security)</bridgehead>
+
<indexterm><primary>Yum</primary><secondary>plugins</secondary><tertiary>yum-plugin-security</tertiary></indexterm>
<para>Discovering information about and applying security updates easily and
often is important to all system administrators. For this reason
<application>Yum</application> provides the
<application>security</application> plugin, which extends
<command>yum</command> with a set of highly-useful security-related commands,
subcommands and options.</para>
<para>You can check for all security-related updates as
follows:</para>
<screen>
@@ -767,6 +807,7 @@ kernel-headers.x86_64 2.6.30.8-64.el6
rhel</screen>
<section
id="sec-Additional_Resources">
<title>Additional Resources</title>
+ <indexterm><primary>Yum</primary><secondary>Additional
Resources</secondary></indexterm>
<variablelist>
<varlistentry>
<term>