web/html/docs/beta/yum-software-management generated-index.php, 1.1, 1.2 index.php, 1.1, 1.2 ln-legalnotice.php, 1.1, 1.2 sn-managing-packages.php, 1.1, 1.2 sn-searching-packages.php, 1.1, 1.2 sn-software-management-concepts.php, 1.1, 1.2 sn-software-management-tools.php, 1.1, 1.2 sn-updating-your-system.php, 1.1, 1.2 sn-using-repositories.php, 1.1, 1.2 sn-yum-installing-frompackage.php, 1.1, 1.2 sn-yum-maintenance.php, 1.1, 1.2 sn-yum-proxy-server.php, 1.1, 1.2
Karsten Wade (kwade)
fedora-extras-commits at redhat.com
Tue Jul 26 01:42:05 UTC 2005
Author: kwade
Update of /cvs/fedora/web/html/docs/beta/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1999
Modified Files:
generated-index.php index.php ln-legalnotice.php
sn-managing-packages.php sn-searching-packages.php
sn-software-management-concepts.php
sn-software-management-tools.php sn-updating-your-system.php
sn-using-repositories.php sn-yum-installing-frompackage.php
sn-yum-maintenance.php sn-yum-proxy-server.php
Log Message:
Updates to beta, style and usage mainly.
Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/index.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.php 25 Jul 2005 19:12:46 -0000 1.1
+++ index.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -7,9 +7,9 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Software Management with yum -
- BETA DOCUMENT</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-software-management-concepts.php">Next</a></td></tr></table><hr></div><div class="article" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="yum-software-management"></a>Software Management with <tt class="command">yum</tt> -
- <span class="emphasis"><em>BETA DOCUMENT</em></span></h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Stuart</span> <span class="surname">Ellis</span></h3></div></div></div><div><p class="copyright">Copyright © 2005 Stuart Ellis</p></div><div><a href="ln-legalnotice.php">Legal Notice</a></div><div><div class="revhistory"><table border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 0.4</td><td align="left">2005-06-01</td><td align="left">StuartEllis</td></tr><tr><td align="left" colspan="3">
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Software Management with yum - BETA
+ DOCUMENT</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-software-management-concepts.php">Next</a></td></tr></table><hr></div><div class="article" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="yum-software-management"></a>Software Management with <tt class="command">yum</tt> - <span class="emphasis"><em>BETA
+ DOCUMENT</em></span></h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Stuart</span> <span class="surname">Ellis</span></h3></div></div></div><div><p class="copyright">Copyright © 2005 Stuart Ellis</p></div><div><a href="ln-legalnotice.php">Legal Notice</a></div><div><div class="revhistory"><table border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 0.4</td><td align="left">2005-06-01</td><td align="left">StuartEllis</td></tr><tr><td align="left" colspan="3">
<p>
Initial import into CVS.
</p>
@@ -17,6 +17,10 @@
<p>
Updated for Fedora Core 4.
</p>
+ </td></tr><tr><td align="left">Revision 0.6</td><td align="left">2005-07-25</td><td align="left">PaulWFrields</td></tr><tr><td align="left" colspan="3">
+ <p>
+ Edited for style and usage; BETA publication.
+ </p>
</td></tr></table></div></div></div><div></div><hr></div><div class="toc"><dl><dt><span class="section"><a href="index.php#sn-introduction">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="index.php#sn-purpose">1.1. Purpose</a></span></dt><dt><span class="section"><a href="index.php#sn-software-management-audience">1.2. Audience</a></span></dt><dt><span class="section"><a href="index.php#sn-software-management-usingdoc">1.3. Using This Document</a></span></dt><dt><span class="section"><a href="index.php#sn-yum-additional-resources">1.4. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sn-software-management-concepts.php">2. Software Management Concepts</a></span></dt><dd><dl><dt><span class="section"><a href="sn-software-management-concepts.php#sn-about-packages">2.1. About Packages</a></span></dt><dt><span class="section"><a href="sn-software-management-concepts.php#sn-about-repositories">2.2. About Repositor!
ies</a></span></dt><dt><span class="section"><a href="sn-software-management-concepts.php#sn-about-dependencies">2.3. About Dependencies</a></span></dt><dt><span class="section"><a href="sn-software-management-concepts.php#sn-package-names">2.4. Understanding Package Names</a></span></dt></dl></dd><dt><span class="section"><a href="sn-software-management-tools.php">3. Software Management Tools in Fedora Core</a></span></dt><dt><span class="section"><a href="sn-managing-packages.php">4. Managing Software with yum</a></span></dt><dd><dl><dt><span class="section"><a href="sn-managing-packages.php#sn-yum-installing-withrepositories">4.1. Installing New Software with yum</a></span></dt><dt><span class="section"><a href="sn-managing-packages.php#sn-yum-updating-withrepositories">4.2. Updating Software with yum</a></span></dt><dt><span class="section"><a href="sn-managing-packages.php#sn-yum-removing-software">4.3. Removing Software with yum</a></span></dt></dl></dd><dt><span clas!
s="section"><a href="sn-searching-packages.php">5. Searching f!
or Pac
es with yum</a></span></dt><dd><dl><dt><span class="section"><a href="sn-searching-packages.php#sn-searching-packages-byname">5.1. Searching by Package Name and Attributes</a></span></dt><dt><span class="section"><a href="sn-searching-packages.php#sn-searching-packages-advanced">5.2. Advanced Searches</a></span></dt><dt><span class="section"><a href="sn-searching-packages.php#sn-package-matches">5.3. Understanding Matches</a></span></dt></dl></dd><dt><span class="section"><a href="sn-updating-your-system.php">6. Updating Your System with yum</a></span></dt><dd><dl><dt><span class="section"><a href="sn-updating-your-system.php#sn-automatic-updating">6.1. Automatically Updating Your System</a></span></dt></dl></dd><dt><span class="section"><a href="sn-using-repositories.php">7. Using Other Software Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="sn-using-repositories.php#sn-adding-repositories">7.1. Adding a Repository as a Package Source</a></span></dt>!
<dt><span class="section"><a href="sn-using-repositories.php#sn-authorizing-package-sources">7.2. Manually Authorizing Package Sources</a></span></dt><dt><span class="section"><a href="sn-using-repositories.php#sn-compat-repositories">7.3. Understanding Repository Compatibility</a></span></dt></dl></dd><dt><span class="section"><a href="sn-yum-maintenance.php">8. Maintaining yum</a></span></dt><dd><dl><dt><span class="section"><a href="sn-yum-maintenance.php#sn-removing-sources">8.1. Disabling or Removing Package Sources</a></span></dt><dt><span class="section"><a href="sn-yum-maintenance.php#sn-yum-clearance">8.2. Clearing the yum Caches</a></span></dt></dl></dd><dt><span class="section"><a href="sn-yum-installing-frompackage.php">9. Manually Installing Software</a></span></dt><dt><span class="section"><a href="sn-yum-proxy-server.php">10. Using yum with a Proxy Server</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="titl!
e" style="clear: both"><a name="sn-introduction"></a>1. I!
ntrodu
on</h2></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: DRAFT"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">DRAFT</th></tr><tr><td colspan="2" align="left" valign="top"><p>
This is a draft version of the document. It is subject to change at any time
and may not have been tested for technical accuracy yet. If you find any
@@ -59,7 +63,7 @@
<tt class="systemitem">root</tt> password. The
example terminal commands use <tt class="command">su
<tt class="option">-c</tt></tt> to provide this facility.
- </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-additional-resources"></a>1.4. Additional Resources</h3></div></div><div></div></div><a class="indexterm" name="id2828382"></a><a class="indexterm" name="id2828394"></a><p>
+ </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-additional-resources"></a>1.4. Additional Resources</h3></div></div><div></div></div><a class="indexterm" name="id2836661"></a><a class="indexterm" name="id2836673"></a><p>
The <tt class="command">yum</tt> utility has features and options not
discussed in this document. Read the <tt class="command">man</tt>
pages for <tt class="command">yum(8)</tt> and
@@ -68,11 +72,11 @@
</p><pre class="screen">
<b class="userinput"><tt>man yum
man yum.conf</tt></b>
-</pre><a class="indexterm" name="id2828448"></a><a class="indexterm" name="id2828460"></a><p>
+</pre><a class="indexterm" name="id2836727"></a><a class="indexterm" name="id2836739"></a><p>
Other useful <tt class="command">yum</tt> resources on the Internet
include:
</p><div class="variablelist"><dl><dt><span class="term">
- Web home page
+ Project web site
</span></dt><dd><p>
<a href="http://linux.duke.edu/projects/yum/" target="_top">http://linux.duke.edu/projects/yum/</a>
</p></dd><dt><span class="term">
Index: ln-legalnotice.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/ln-legalnotice.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ln-legalnotice.php 25 Jul 2005 19:12:46 -0000 1.1
+++ ln-legalnotice.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -26,7 +26,7 @@
They all may be freely redistributed with documentation
produced for the Fedora Project.
</p><p>
- yum-software-management-0.5.0 (2005-07-19)
+ yum-software-management-0.6 (2005-07-25)
</p><p>
Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux
Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts,
Index: sn-managing-packages.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/sn-managing-packages.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-managing-packages.php 25 Jul 2005 19:12:46 -0000 1.1
+++ sn-managing-packages.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -7,35 +7,25 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4. Managing Software with yum</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-software-management-tools.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-searching-packages.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-managing-packages"></a>4. Managing Software with <tt class="command">yum</tt></h2></div></div><div></div></div><a class="indexterm" name="id2829100"></a><p>
- The <tt class="command">yum</tt> utility may modify the software on your
- system in three ways:
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">4. Managing Software with yum</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-software-management-tools.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-searching-packages.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-managing-packages"></a>4. Managing Software with <tt class="command">yum</tt></h2></div></div><div></div></div><a class="indexterm" name="id2837451"></a><p>
+ Use the <tt class="command">yum</tt> utility to modify the software on
+ your system in three ways:
</p><p>
</p><div class="itemizedlist"><ul type="disc"><li><p>
- It may install new software from repositories or a package
- file.
+ To install new software from repositories or a package file
</p></li><li><p>
- It may update existing software on your system.
+ To update existing software on your system
</p></li><li><p>
- It may remove unwanted software from your system.
+ To remove unwanted software from your system
</p></li></ul></div><p>
</p><p>
To use <tt class="command">yum</tt>, specify a function and one or more
packages or package groups. Each section below gives some
examples.
- </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Package Names"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">Package Names</th></tr><tr><td colspan="2" align="left" valign="top"><p>
- You may use any of the following formats to specify a package in
- a <tt class="command">yum</tt> operation: <i class="replaceable"><tt>name</tt></i>,
- <i class="replaceable"><tt>name.architecture</tt></i>,
- <i class="replaceable"><tt>name-version</tt></i>,
- <i class="replaceable"><tt>name-version-release</tt></i>,
- <i class="replaceable"><tt>name-version-release.architecture</tt></i>, and
- <i class="replaceable"><tt>epoch:name-version-release.architecture</tt></i>.
- </p></td></tr></table></div><p>
- To use the repositories <tt class="command">yum</tt> downloads data
- files from each of the configured repositories. On a slow
- connection, it may take several seconds to download the required
- files for each package.
+ </p><p>
+ <tt class="command">yum</tt> downloads data files from each of the
+ configured repositories. On a slow connection, it may take several
+ seconds to download the required files for each package.
</p><p>
During operation, <tt class="command">yum</tt> first determines the best
set of actions to produce the required result, and displays the
@@ -44,8 +34,8 @@
additional packages in addition to the package that you specified.
These actions may be necessary to resolve software dependencies.
</p><div class="example"><a name="yum-transaction-format"></a><p>
- This is an example of the transaction for installing
- <tt class="filename">tsclient</tt>:
+ This is an example of the transaction for installing
+ <tt class="filename">tsclient</tt>:
</p><pre class="screen">
<tt class="computeroutput">=============================================================================
Package Arch Version Repository Size
@@ -63,24 +53,27 @@
Total download size: 355 k
Is this ok [y/N]:</tt>
</pre><p class="title"><b>Example 1. Format of <tt class="command">yum</tt> Transaction Reports</b></p></div><p>
- Review the list of changes, and then press <span><b class="keycap">y</b></span> to
- accept and begin the process. If you press <span><b class="keycap">N</b></span> or
- <span><b class="keycap">Enter</b></span>, <tt class="command">yum</tt> does not download
- or change any packages.
+ Review the list of changes, and then press
+ <span><b class="keycap">y</b></span>
+ to accept and begin the process. If you press
+ <span><b class="keycap">N</b></span>
+ or
+ <span><b class="keycap">Enter</b></span>
+ , <tt class="command">yum</tt> does not download or change any packages.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Package Versions"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Package Versions</th></tr><tr><td colspan="2" align="left" valign="top"><p>
The <tt class="command">yum</tt> utility only displays and uses the
- newest version of each package, unless you specify an older
- version.
+ newest version of each package, unless you specify an older
+ version.
</p></td></tr></table></div><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Downloads are Cached"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">Downloads are Cached</th></tr><tr><td colspan="2" align="left" valign="top"><p>
The <tt class="command">yum</tt> utility keeps Downloaded data files
- and packages for reuse. You may copy packages from the
- repository cache directories under
- <tt class="filename">/var/cache/yum/</tt>, and use them elsewhere if
- you wish. If you remove a package from the cache, you do not
- affect the copy of the software installed on your system.
- </p></td></tr></table></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-installing-withrepositories"></a>4.1. Installing New Software with <tt class="command">yum</tt></h3></div></div><div></div></div><a class="indexterm" name="id2829373"></a><a class="indexterm" name="id2829386"></a><p>
+ and packages for reuse. You may copy packages from the
+ repository cache directories under
+ <tt class="filename">/var/cache/yum/</tt>, and use them elsewhere if
+ you wish. If you remove a package from the cache, you do not
+ affect the copy of the software installed on your system.
+ </p></td></tr></table></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-installing-withrepositories"></a>4.1. Installing New Software with <tt class="command">yum</tt></h3></div></div><div></div></div><a class="indexterm" name="id2837683"></a><a class="indexterm" name="id2837696"></a><p>
To install the package <tt class="filename">tsclient</tt>, enter the
- command:
+ command:
</p><pre class="screen">
<b class="userinput"><tt>su -c 'yum install <i class="replaceable"><tt>tsclient</tt></i>'</tt></b>
</pre><p>
@@ -98,10 +91,12 @@
prompted.
</p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: New Services Require Activation"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td><th align="left">New Services Require Activation</th></tr><tr><td colspan="2" align="left" valign="top"><p>
When you install a service, Fedora does not activate or start
- it. To configure a new service to run on bootup, choose
- <span><b class="guimenu">Desktop</b></span>-><span><b class="guisubmenu">System Settings</b></span>-><span><b class="guisubmenu">Server Settings</b></span>-><span><b class="guimenuitem">Services</b></span>, or use the <tt class="command">chkconfig</tt>
- and <tt class="command">service</tt> command-line utilities.
- </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-updating-withrepositories"></a>4.2. Updating Software with <tt class="command">yum</tt></h3></div></div><div></div></div><a class="indexterm" name="id2829547"></a><a class="indexterm" name="id2829559"></a><p>
+ it. To configure a new service to run on bootup, choose
+ <span><b class="guimenu">Desktop</b></span>-><span><b class="guisubmenu">System
+ Settings</b></span>-><span><b class="guisubmenu">Server Settings</b></span>-><span><b class="guimenuitem">Services</b></span>, or use the
+ <tt class="command">chkconfig</tt> and <tt class="command">service</tt>
+ command-line utilities.
+ </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-updating-withrepositories"></a>4.2. Updating Software with <tt class="command">yum</tt></h3></div></div><div></div></div><a class="indexterm" name="id2837856"></a><a class="indexterm" name="id2837869"></a><p>
To update the <tt class="filename">tsclient</tt> package to the
latest version, type:
</p><pre class="screen">
@@ -112,8 +107,8 @@
prompted.
</p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: New Software Versions Require Reloading"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td><th align="left">New Software Versions Require Reloading</th></tr><tr><td colspan="2" align="left" valign="top"><p>
If a piece of software is in use when you update it, the old
- version remains active until the software is restarted. Kernel
- updates take effect when you reboot the system.
+ version remains active until the software is restarted. Kernel
+ updates take effect when you reboot the system.
</p></td></tr></table></div><p>
To update all of the packages in the package group
<tt class="filename">MySQL Database</tt>, enter the command:
@@ -125,9 +120,9 @@
prompted.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Updating the Entire System"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Updating the Entire System</th></tr><tr><td colspan="2" align="left" valign="top"><p>
To update all of the packages on your Fedora system, use the
- commands described in
+ commands described in
<a href="sn-updating-your-system.php" title="6. Updating Your System with yum">Section 6, “Updating Your System with yum”</a>.
- </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-removing-software"></a>4.3. Removing Software with <tt class="command">yum</tt></h3></div></div><div></div></div><a class="indexterm" name="id2829696"></a><a class="indexterm" name="id2829705"></a><p>
+ </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-removing-software"></a>4.3. Removing Software with <tt class="command">yum</tt></h3></div></div><div></div></div><a class="indexterm" name="id2838007"></a><a class="indexterm" name="id2838016"></a><p>
To remove software, <tt class="command">yum</tt> examines your system
for both the specified software, and any software which claims
it as a dependency.
Index: sn-searching-packages.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/sn-searching-packages.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-searching-packages.php 25 Jul 2005 19:12:46 -0000 1.1
+++ sn-searching-packages.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -7,24 +7,24 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5. Searching for Packages with yum</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-managing-packages.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-updating-your-system.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-searching-packages"></a>5. Searching for Packages with <tt class="command">yum</tt></h2></div></div><div></div></div><a class="indexterm" name="id2829823"></a><a class="indexterm" name="id2829835"></a><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5. Searching for Packages with yum</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-managing-packages.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-updating-your-system.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-searching-packages"></a>5. Searching for Packages with <tt class="command">yum</tt></h2></div></div><div></div></div><a class="indexterm" name="id2838134"></a><a class="indexterm" name="id2838146"></a><p>
Use the search features of <tt class="command">yum</tt> to find software
that is available from the configured repositories, or already
installed on your system. Searches automatically include both
installed and available packages.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Searches are not Case-sensitive"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Searches are not Case-sensitive</th></tr><tr><td colspan="2" align="left" valign="top"><p>
The <tt class="option">search</tt> and <tt class="option">list</tt> options of
- <tt class="command">yum</tt> are not case-sensitive. A query for
- <tt class="filename">palmpilot</tt> automatically finds
- <tt class="filename">PalmPilot</tt> packages.
+ <tt class="command">yum</tt> are not case-sensitive. A query for
+ <tt class="filename">palmpilot</tt> automatically finds
+ <tt class="filename">PalmPilot</tt> packages.
</p></td></tr></table></div><p>
The format of the results depends upon the option. If the query
produces no information, there are no packages matching the
criteria.
</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-searching-packages-byname"></a>5.1. Searching by Package Name and Attributes</h3></div></div><div></div></div><p>
To search for a specific package by name, use the
- <tt class="option">list</tt> function. To search for the package
- <tt class="filename">tsclient</tt>, use the command:
+ <tt class="option">list</tt> function. To search for the package
+ <tt class="filename">tsclient</tt>, use the command:
</p><pre class="screen">
<b class="userinput"><tt>su -c 'yum list <i class="replaceable"><tt>tsclient</tt></i>'</tt></b>
</pre><p>
@@ -33,8 +33,8 @@
prompted.
</p><p>
To make your queries more specific, add other package
- attributes. To search for version 0.132 of the application, use
- the command:
+ attributes. To search for version 0.132 of the application, use
+ the command:
</p><pre class="screen">
<b class="userinput"><tt>su -c 'yum list <i class="replaceable"><tt>tsclient-0.132</tt></i>'</tt></b>
</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-searching-packages-advanced"></a>5.2. Advanced Searches</h3></div></div><div></div></div><p>
@@ -42,9 +42,9 @@
<tt class="option">search</tt> or <tt class="option">provides</tt> options.
</p><p>
The <tt class="option">search</tt> option checks the names,
- descriptions, summaries and listed package maintainers of all of
- the available packages to find those that match. For example, to
- search for all packages that relate to PalmPilots, type:
+ descriptions, summaries and listed package maintainers of all of
+ the available packages to find those that match. For example, to
+ search for all packages that relate to PalmPilots, type:
</p><pre class="screen">
<b class="userinput"><tt>su -c 'yum search <i class="replaceable"><tt>PalmPilot</tt></i>'</tt></b>
</pre><p>
@@ -64,8 +64,8 @@
<b class="userinput"><tt>su -c 'yum provides <i class="replaceable"><tt>libneon</tt></i>'</tt></b>
</pre><p>
To search for all packages that either provide a MTA (Mail
- Transport Agent) service, or include files with
- <tt class="filename">mta</tt> in their name:
+ Transport Agent) service, or include files with
+ <tt class="filename">mta</tt> in their name:
</p><pre class="screen">
<b class="userinput"><tt>su -c 'yum provides <i class="replaceable"><tt>MTA</tt></i>'</tt></b>
</pre><p>
@@ -73,22 +73,22 @@
<tt class="systemitem">root</tt> account.
</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Wildcards and Regular Expressions"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">Wildcards and Regular Expressions</th></tr><tr><td colspan="2" align="left" valign="top"><p>
You may use the standard wildcard characters in search
- criteria: <tt class="option">?</tt> to represent any one character,
- and <tt class="option">*</tt> to mean zero or more characters. Use
- Perl or Python regular expressions to carry out more complex
- queries.
+ criteria: <tt class="option">?</tt> to represent any one character,
+ and <tt class="option">*</tt> to mean zero or more characters. Use
+ Perl or Python regular expressions to carry out more complex
+ queries.
</p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-package-matches"></a>5.3. Understanding Matches</h3></div></div><div></div></div><p>
Searches with <tt class="command">yum</tt> show all of the packages
- that match your criteria. Packages must meet the terms of the
- search exactly to be considered matches, unless you use
- wildcards or a regular expression.
+ that match your criteria. Packages must meet the terms of the
+ search exactly to be considered matches, unless you use
+ wildcards or a regular expression.
</p><p>
For example, a search query for <tt class="filename">shadowutils</tt>
- or <tt class="filename">shadow-util</tt> would not produce the
- package <tt class="filename">shadow-utils</tt>. This package would
- match and be shown if the query was either
- <tt class="filename">shadow-util?</tt> or
- <tt class="filename">Shadow*</tt>.
+ or <tt class="filename">shadow-util</tt> would not produce the
+ package <tt class="filename">shadow-utils</tt>. This package would
+ match and be shown if the query was either
+ <tt class="filename">shadow-util?</tt> or
+ <tt class="filename">Shadow*</tt>.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-managing-packages.php">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.php">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sn-updating-your-system.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4. Managing Software with yum </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 6. Updating Your System with yum</td></tr></table></div>
<?
Index: sn-software-management-concepts.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/sn-software-management-concepts.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-software-management-concepts.php 25 Jul 2005 19:12:46 -0000 1.1
+++ sn-software-management-concepts.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -7,133 +7,162 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2. Software Management Concepts</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-software-management-tools.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-software-management-concepts"></a>2. Software Management Concepts</h2></div></div><div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-about-packages"></a>2.1. About Packages</h3></div></div><div></div></div><a class="indexterm" name="id2828580"></a><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2. Software Management Concepts</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-software-management-tools.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-software-management-concepts"></a>2. Software Management Concepts</h2></div></div><div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-about-packages"></a>2.1. About Packages</h3></div></div><div></div></div><a class="indexterm" name="id2836864"></a><p>
Fedora software and documentation is supplied in the form of
- files called RPM <i class="firstterm">packages</i>. Each package
- is a compressed archive containing product information, program
- files, icons, documentation and management scripts. Management
- applications use these files to safely locate, install, update
- and remove software. For example, the Fedora installation process
- uses the packages supplied with Fedora Core to build or upgrade a
- system to your requirements.
+ files called RPM <i class="firstterm">packages</i>. Each package
+ is a compressed archive containing product information, program
+ files, icons, documentation and management scripts. Management
+ applications use these files to safely locate, install, update
+ and remove software. For example, the Fedora installation process
+ uses the packages supplied with Fedora Core to build or upgrade a
+ system to your requirements.
</p><p>
Packages also include a digital signature to prove their source.
- Software management utilities verify this digital signature by
- using a GPG <i class="firstterm">public key</i>. The
- <tt class="command">yum</tt> and <tt class="command">rpm</tt> utilities
- share a common <i class="firstterm">keyring</i> that stores all of
- the public keys for approved package sources. The system
- administrator configures these approved package sources.
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-about-repositories"></a>2.2. About Repositories</h3></div></div><div></div></div><a class="indexterm" name="id2766544"></a><p>
+ Software management utilities verify this digital signature by
+ using a GPG <i class="firstterm">public key</i>. The
+ <tt class="command">yum</tt> and <tt class="command">rpm</tt> utilities
+ share a common <i class="firstterm">keyring</i> that stores all of
+ the public keys for approved package sources. The system
+ administrator configures these approved package sources.
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-about-repositories"></a>2.2. About Repositories</h3></div></div><div></div></div><a class="indexterm" name="id2774832"></a><p>
A <i class="firstterm">repository</i> is a prepared directory or
web site that contains software packages and index files.
Software management utilities such as <tt class="command">yum</tt>
automatically locate and obtain the correct RPM packages from
these repositories. This method frees you from having to
- manually find and install new applications or updates. You may
+ manually find and install new applications or updates. You may
use a single command to update all system software, or search
for new software by specifying criteria. In each case the
management utility connects to the configured repositories and
checks their indexes to find the correct packages.
</p><p>
The package management utilities in Fedora Core are already configured
- to use the network of repositories maintained by the Fedora Project. These
- repositories contain the software included with Fedora Core and a large
- selection of additional software known as Fedora Extras. Third-party
- software developers also provide repositories for their Fedora
- compatible packages.
+ to use the network of repositories maintained by the Fedora Project. These
+ repositories contain the software included with Fedora Core and a large
+ selection of additional software known as Fedora Extras. Third-party
+ software developers also provide repositories for their Fedora
+ compatible packages.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: All Fedora Packages are Open Source Software"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">All Fedora Packages are Open Source Software</th></tr><tr><td colspan="2" align="left" valign="top"><p>
All of the software provided by the Fedora Project is open source
- software. You may download and install software from the Fedora Project
- network of repositories on as many systems as desired.
- </p></td></tr></table></div><a class="indexterm" name="id2766603"></a><p>
+ software. You may download and install software from the Fedora Project
+ network of repositories on as many systems as desired.
+ </p></td></tr></table></div><a class="indexterm" name="id2774879"></a><p>
You may also use the <i class="firstterm">package groups</i>
- provided by the Fedora repositories to manage related packages as
- sets. Some third-party repositories add packages to these
- groups, or provide their packages as additional groups.
+ provided by the Fedora repositories to manage related packages as
+ sets. Some third-party repositories add packages to these
+ groups, or provide their packages as additional groups.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Available Package Groups"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Available Package Groups</th></tr><tr><td colspan="2" align="left" valign="top"><p>
To view a list of all of the available package groups for your
- Fedora system, run the command <tt class="command">yum
- grouplist</tt>.
+ Fedora system, run the command <tt class="command">su -c 'yum
+ grouplist'</tt>.
</p></td></tr></table></div><p>
Use repositories to ensure that you always receive current
- versions of software. If several versions of the same package
- are available, your management utility automatically selects the
- latest version.
+ versions of software. If several versions of the same package
+ are available, your management utility automatically selects the
+ latest version.
</p><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Caution: Installing Software not from a Repository"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="./stylesheet-images/caution.png"></td><th align="left">Installing Software not from a Repository</th></tr><tr><td colspan="2" align="left" valign="top"><p>
- Install software using manual methods only when you are
- confident there is no repository which can currently provide
- it. You may have to manage that software with manual methods,
- instead of with Fedora software management utilities.
- </p><p>
+ Install software using manual methods only when you are
+ confident there is no repository which can currently provide
+ it. You may have to manage that software with manual methods,
+ instead of with Fedora software management utilities.
+ </p><p>
The <tt class="command">yum</tt> commands shown in this document use
- repositories as package sources. Refer to
+ repositories as package sources. Refer to
<a href="sn-yum-installing-frompackage.php" title="9. Manually Installing Software">Section 9, “Manually Installing Software”</a> for details of
- using <tt class="command">yum</tt> to install software from a
- package file.
- </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-about-dependencies"></a>2.3. About Dependencies</h3></div></div><div></div></div><a class="indexterm" name="id2766687"></a><p>
- Some of the files installed on a Fedora distribution are
- <i class="firstterm">libraries</i> which may provide functions to
- multiple applications. When an application requires a specific
- library, the package which contains that library is a
- <i class="firstterm">dependency</i>. To properly install a
- package, Fedora must first satisfy its dependencies. The
- dependency information for a RPM package is stored within the
- RPM file.
+ using <tt class="command">yum</tt> to install software from a
+ package file.
+ </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-about-dependencies"></a>2.3. About Dependencies</h3></div></div><div></div></div><a class="indexterm" name="id2774986"></a><p>
+ Some of the files installed on a Fedora distribution are
+ <i class="firstterm">libraries</i> which may provide functions to
+ multiple applications. When an application requires a specific
+ library, the package which contains that library is a
+ <i class="firstterm">dependency</i>. To properly install a
+ package, Fedora must first satisfy its dependencies. The
+ dependency information for a RPM package is stored within the
+ RPM file.
</p><p>
The <tt class="command">yum</tt> utility uses package dependency data
- to ensure all its requirements are met during installation. The
- <tt class="command">yum</tt> utility automatically installs packages
- for any required software not already present on your system. If
- a new application has requirements that conflict with existing
- software, <tt class="command">yum</tt> aborts without making any
- changes to your system.
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-package-names"></a>2.4. Understanding Package Names</h3></div></div><div></div></div><a class="indexterm" name="id2767906"></a><a class="indexterm" name="id2767919"></a><p>
+ to ensure that all of requirements for an application are met
+ during installation. It automatically installs the packages for
+ any dependencies not already present on your system. If a new
+ application has requirements that conflict with existing
+ software, <tt class="command">yum</tt> aborts without making any
+ changes to your system.
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-package-names"></a>2.4. Understanding Package Names</h3></div></div><div></div></div><a class="indexterm" name="id2775048"></a><a class="indexterm" name="id2776165"></a><p>
Each package file has a long name that indicates several key
- pieces of information. This is the full name of the
- <tt class="filename">tsclient</tt> package supplied with Fedora Core:
+ pieces of information. This is the full name of the
+ <tt class="filename">tsclient</tt> package supplied with Fedora Core:
</p><pre class="screen">
<tt class="filename">tsclient-0.132-4.i386.rpm</tt>
</pre><p>
- These naming conventions are valid for the file shown above:
+ Management utilities refer to packages with one of three
+ formats:
</p><div class="itemizedlist"><ul type="disc"><li><p>
Package name: <tt class="filename">tsclient</tt>
</p></li><li><p>
Package name with version and release numbers:
- <tt class="filename">tsclient-0.132-4</tt>
+ <tt class="filename">tsclient-0.132-4</tt>
</p></li><li><p>
Package name with hardware architecture:
- <tt class="filename">tsclient.i386</tt>
+ <tt class="filename">tsclient.i386</tt>
</p></li></ul></div><p>
- Use only the name of the package with <tt class="command">yum</tt>,
- except when the exact version or type is necessary. <i><span class="remark">When exactly is that required? I fixed the
- sentence structure but the meaning is obscure here. Tell the
- reader the full story here. [PWF]</span></i> For example, use
- <tt class="filename">name-version</tt> to specify the exact version
- of the application. The package listings provided by
- <tt class="command">yum</tt> use the format
- <tt class="filename">name.architecture</tt> to specify the type of
- computer for which the package is intended.
+ For clarity, <tt class="command">yum</tt> itself lists packages in the
+ format <tt class="filename">name.architecture</tt>. Repositories also
+ commonly store packages in separate directories by architecture.
+ In each case, the hardware architecture specified for the
+ package is the <span class="emphasis"><em>minimum</em></span> type of machine
+ required to use the package.
+ </p><div class="variablelist"><dl><dt><span class="term">
+ i386
+ </span></dt><dd><p>
+ Suitable for any current Intel-compatible computer
+ </p></dd><dt><span class="term">
+ noarch
+ </span></dt><dd><p>
+ Compatible with all computer architectures
+ </p></dd><dt><span class="term">
+ ppc
+ </span></dt><dd><p>
+ Suitable for PowerPC systems, such as Apple Power
+ Macintosh
+ </p></dd><dt><span class="term">
+ x86_64
+ </span></dt><dd><p>
+ Suitable for 64-bit Intel-compatible processors, such as
+ Opterons
+ </p></dd></dl></div><p>
+ Some software may be optimized for particular types of
+ Intel-compatible machine. Separate packages may be provided for
+ <tt class="option">i386</tt>, <tt class="option">i586</tt>,
+ <tt class="option">i686</tt> and <tt class="option">x86_64</tt> computers. A
+ machine with at least an Intel Pentium, VIA C3 or compatible CPU
+ may use <tt class="option">i586</tt> packages. Computers with an Intel
+ Pentium Pro and above, or a current model of AMD chip, may use
+ <tt class="option">i686</tt> packages.
</p><p>
- The hardware architecture is the <span class="emphasis"><em>minimum</em></span>
- type of machine required for that specific package. Packages
- with architecture <tt class="option">i386</tt> run on any current
- Intel-compatible computer. Packages for PowerPC systems, such as
- Apple Power Macintosh, are indicated with <tt class="option">ppc</tt>.
- Packages for systems with 64-bit processors such as Opterons are
- indicated with <tt class="option">x86_64</tt>. Packages specified as
- <tt class="option">noarch</tt> have no architecture requirement.
+ Use the short name of the package for <tt class="command">yum</tt>
+ commands. This causes <tt class="command">yum</tt> to automatically
+ select the most recent package in the repositories that matches
+ the hardware architecture of your computer.
</p><p>
- Some software may be optimized for particular types of
- Intel-compatible machine. Separate packages may be provided for
- <tt class="option">i386</tt>, <tt class="option">i586</tt>,
- <tt class="option">i686</tt> and <tt class="option">x86_64</tt> computers. A
- machine with at least an Intel Pentium, VIA C3 or compatible CPU
- may use <tt class="option">i586</tt> packages. Computers with an Intel
- Pentium Pro and above, or a current model of AMD chip, may use
- <tt class="option">i686</tt> packages.
- </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.php">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sn-software-management-tools.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Software Management with yum -
- BETA DOCUMENT </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 3. Software Management Tools in Fedora Core</td></tr></table></div>
+ Specify a package with other name formats to override the
+ default behavior and force <tt class="command">yum</tt> to use the
+ package that matches that version or architecture. Only override
+ <tt class="command">yum</tt> when you know that the default package
+ selection has a bug or other fault that makes it unsuitable for
+ installation.
+ </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Package Names"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">Package Names</th></tr><tr><td colspan="2" align="left" valign="top"><p>
+ You may use any of the following formats to specify a package
+ in a <tt class="command">yum</tt> operation:
+ <i class="replaceable"><tt>name</tt></i>,
+ <i class="replaceable"><tt>name.architecture</tt></i>,
+ <i class="replaceable"><tt>name-version</tt></i>,
+ <i class="replaceable"><tt>name-version-release</tt></i>,
+ <i class="replaceable"><tt>name-version-release.architecture</tt></i>,
+ and
+ <i class="replaceable"><tt>epoch:name-version-release.architecture</tt></i>.
+ </p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.php">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.php">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sn-software-management-tools.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Software Management with yum - BETA
+ DOCUMENT </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 3. Software Management Tools in Fedora Core</td></tr></table></div>
<?
Index: sn-software-management-tools.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/sn-software-management-tools.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-software-management-tools.php 25 Jul 2005 19:12:46 -0000 1.1
+++ sn-software-management-tools.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -7,7 +7,7 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3. Software Management Tools in Fedora Core</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-software-management-concepts.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-managing-packages.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-software-management-tools"></a>3. Software Management Tools in Fedora Core</h2></div></div><div></div></div><a class="indexterm" name="id2768134"></a><a class="indexterm" name="id2768143"></a><a class="indexterm" name="id2768152"></a><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3. Software Management Tools in Fedora Core</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-software-management-concepts.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-managing-packages.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-software-management-tools"></a>3. Software Management Tools in Fedora Core</h2></div></div><div></div></div><a class="indexterm" name="id2837264"></a><a class="indexterm" name="id2837273"></a><a class="indexterm" name="id2837282"></a><p>
The <tt class="command">yum</tt> utility is a complete software
management system. Fedora Core also includes other several other
applications that can supplement <tt class="command">yum</tt>.
@@ -21,9 +21,10 @@
</p><p>
Fedora Core also includes
<span><b class="application">system-config-packages</b></span>. To run this
- application from the graphical interface, select
- <span><b class="guimenu">Desktop</b></span>-><span><b class="guisubmenu">System Settings</b></span>-><span><b class="guimenuitem">Add/Remove Applications</b></span>. Unlike <span><b class="application">up2date</b></span> and
- <tt class="command">yum</tt>,
+ application from the graphical interface, select <span><b class="guimenu">Desktop</b></span>-><span><b class="guisubmenu">System
+ Settings</b></span>-><span><b class="guimenuitem">Add/Remove
+ Applications</b></span>. Unlike
+ <span><b class="application">up2date</b></span> and <tt class="command">yum</tt>,
<span><b class="application">system-config-packages</b></span> installs
software packages from your Fedora Core installation discs only, and does
not use repositories. This application is used on systems that do
@@ -38,9 +39,9 @@
software.
</p><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Caution: Current Package Versions"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Caution]" src="./stylesheet-images/caution.png"></td><th align="left">Current Package Versions</th></tr><tr><td colspan="2" align="left" valign="top"><p>
The <span><b class="application">up2date</b></span> and
- <tt class="command">yum</tt> utilities ensure that you have the most
- recent version of software packages. Other methods do not
- guarantee that the packages are current.
+ <tt class="command">yum</tt> utilities ensure that you have the most
+ recent version of software packages. Other methods do not
+ guarantee that the packages are current.
</p></td></tr></table></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-software-management-concepts.php">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.php">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sn-managing-packages.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2. Software Management Concepts </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 4. Managing Software with yum</td></tr></table></div>
<?
Index: sn-updating-your-system.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/sn-updating-your-system.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-updating-your-system.php 25 Jul 2005 19:12:46 -0000 1.1
+++ sn-updating-your-system.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -7,7 +7,7 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6. Updating Your System with yum</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-searching-packages.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-using-repositories.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-updating-your-system"></a>6. Updating Your System with <tt class="command">yum</tt></h2></div></div><div></div></div><a class="indexterm" name="id2830222"></a><a class="indexterm" name="id2830234"></a><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6. Updating Your System with yum</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-searching-packages.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-using-repositories.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-updating-your-system"></a>6. Updating Your System with <tt class="command">yum</tt></h2></div></div><div></div></div><a class="indexterm" name="id2838535"></a><a class="indexterm" name="id2838548"></a><p>
Use the <tt class="option">update</tt> option to upgrade all of your
Fedora system software to the latest version with one operation.
</p><p>
@@ -15,11 +15,12 @@
</p><pre class="screen">
<b class="userinput"><tt>su -c 'yum update'</tt></b>
</pre><p>
- At the prompt, enter the <tt class="systemitem">root</tt> password.
- </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-automatic-updating"></a>6.1. Automatically Updating Your System</h3></div></div><div></div></div><a class="indexterm" name="id2830295"></a><p>
+ At the prompt, enter the
+ <tt class="systemitem">root</tt> password.
+ </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-automatic-updating"></a>6.1. Automatically Updating Your System</h3></div></div><div></div></div><a class="indexterm" name="id2838608"></a><p>
The <tt class="filename">yum</tt> package supplied with Fedora Core includes
- scripts to perform full system updates every day. To activate
- automatic daily updates, enter this command:
+ scripts to perform full system updates every day. To activate
+ automatic daily updates, enter this command:
</p><pre class="screen">
<b class="userinput"><tt>su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start'</tt></b>
</pre><p>
@@ -27,12 +28,12 @@
<tt class="systemitem">root</tt> account.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: How Daily Updates are Run"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">How Daily Updates are Run</th></tr><tr><td colspan="2" align="left" valign="top"><p>
There is no separate <tt class="command">yum</tt> service that runs
- on your system. The command given above enables the control
- script <tt class="filename">/etc/rc.d/init.d/yum</tt>. This control
- script activates the script
- <tt class="filename">/etc/cron.daily/yum.cron</tt>, which causes
- the <tt class="command">cron</tt> service to perform the system
- update automatically each day.
+ on your system. The command given above enables the control
+ script <tt class="filename">/etc/rc.d/init.d/yum</tt>. This control
+ script activates the script
+ <tt class="filename">/etc/cron.daily/yum.cron</tt>, which causes
+ the <tt class="command">cron</tt> service to perform the system
+ update automatically each day.
</p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-searching-packages.php">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.php">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sn-using-repositories.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5. Searching for Packages with yum </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 7. Using Other Software Repositories</td></tr></table></div>
<?
Index: sn-using-repositories.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/sn-using-repositories.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-using-repositories.php 25 Jul 2005 19:12:46 -0000 1.1
+++ sn-using-repositories.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -7,21 +7,23 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">7. Using Other Software Repositories</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-updating-your-system.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-yum-maintenance.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-using-repositories"></a>7. Using Other Software Repositories</h2></div></div><div></div></div><a class="indexterm" name="id2830392"></a><a class="indexterm" name="id2830401"></a><a class="indexterm" name="id2830414"></a><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">7. Using Other Software Repositories</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-updating-your-system.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-yum-maintenance.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-using-repositories"></a>7. Using Other Software Repositories</h2></div></div><div></div></div><a class="indexterm" name="id2838706"></a><a class="indexterm" name="id2838715"></a><a class="indexterm" name="id2838727"></a><p>
Fedora systems automatically use the Fedora Project repositories. These
include Fedora Extras, the default source of packages for software that is
not included with Fedora Core.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Fedora Extras Repositories for Previous Versions of Fedora Core"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Fedora Extras Repositories for Previous Versions of Fedora Core</th></tr><tr><td colspan="2" align="left" valign="top"><p>
You must manually configure Fedora 3 systems to use Fedora Extras, using
- the instructions at <a href="http://fedora.redhat.com/projects/extras/" target="_top">http://fedora.redhat.com/projects/extras/</a>. For
- additional packages for Fedora 1 and Fedora 2, refer to <a href="http://www.fedora.us/" target="_top">http://www.fedora.us/</a>.
+ the instructions at
+ <a href="http://fedora.redhat.com/projects/extras/" target="_top">http://fedora.redhat.com/projects/extras/</a>. For
+ additional packages for Fedora 1 and Fedora 2, refer to
+ <a href="http://www.fedora.us/" target="_top">http://www.fedora.us/</a>.
</p></td></tr></table></div><p>
If the Fedora Project does not provide a specific software package, the
manufacturer of the software may provide or recommend a separate
repository. Members of the community also maintain repositories to
provide packages for Fedora systems. Third-party repositories
provide information on their web sites.
- </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-adding-repositories"></a>7.1. Adding a Repository as a Package Source</h3></div></div><div></div></div><a class="indexterm" name="id2830477"></a><p>
+ </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-adding-repositories"></a>7.1. Adding a Repository as a Package Source</h3></div></div><div></div></div><a class="indexterm" name="id2838791"></a><p>
To add an extra repository, place a definition file in the
<tt class="filename">/etc/yum.repos.d/</tt> directory on your system.
Package providers make the definition files for their
@@ -31,9 +33,9 @@
<tt class="filename">.repo</tt>.
</p></td></tr></table></div><p>
You must have <tt class="systemitem">root</tt>
- access to add a file to the definitions directory. To copy the
- definition file <tt class="filename">example.repo</tt>, type this
- command:
+ access to add a file to the definitions directory. To copy the
+ definition file <tt class="filename">example.repo</tt>, type this
+ command:
</p><pre class="screen">
<b class="userinput"><tt>su -c 'cp example.repo /etc/yum.repos.d/'</tt></b>
</pre><p>
@@ -41,25 +43,25 @@
<tt class="systemitem">root</tt> account.
</p><p>
The configuration file for each repository should include a
- <tt class="command">gpgkey</tt> 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 you install software from the repository. If the
- configuration file provided does not include this setting, refer
- to <a href="sn-using-repositories.php#sn-authorizing-package-sources" title="7.2. Manually Authorizing Package Sources">Section 7.2, “Manually Authorizing Package Sources”</a>.
+ <tt class="command">gpgkey</tt> 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 you install software from the repository. If the
+ configuration file provided does not include this setting, refer
+ to <a href="sn-using-repositories.php#sn-authorizing-package-sources" title="7.2. Manually Authorizing Package Sources">Section 7.2, “Manually Authorizing Package Sources”</a>.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Repositories and up2date Channels"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Repositories and up2date Channels</th></tr><tr><td colspan="2" align="left" valign="top"><p>
Starting with Fedora 4, <tt class="command">yum</tt> repositories are
- automatically used as <span><b class="application">up2date</b></span>
- channels. On Fedora 3 and earlier systems, you must manually
- configure <span><b class="application">up2date</b></span> to use these
- channels. To do so, edit the
- <tt class="filename">/etc/sysconfig/rhn/sources</tt> file.
- </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-authorizing-package-sources"></a>7.2. Manually Authorizing Package Sources</h3></div></div><div></div></div><a class="indexterm" name="id2830641"></a><p>
+ automatically used as <span><b class="application">up2date</b></span>
+ channels. On Fedora 3 and earlier systems, you must manually
+ configure <span><b class="application">up2date</b></span> to use these
+ channels. To do so, edit the
+ <tt class="filename">/etc/sysconfig/rhn/sources</tt> file.
+ </p></td></tr></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-authorizing-package-sources"></a>7.2. Manually Authorizing Package Sources</h3></div></div><div></div></div><a class="indexterm" name="id2838958"></a><p>
To manually add a public key to your <tt class="command">rpm</tt>
- keyring, use the <tt class="option">import</tt> feature of the
- <tt class="command">rpm</tt> utility. To import the file
- <tt class="filename">GPG-PUB-KEY.asc</tt>, type the following
- command:
+ keyring, use the <tt class="option">import</tt> feature of the
+ <tt class="command">rpm</tt> utility. To import the file
+ <tt class="filename">GPG-PUB-KEY.asc</tt>, type the following
+ command:
</p><pre class="screen">
<b class="userinput"><tt>su -c 'rpm --import <i class="replaceable"><tt>GPG-PUB-KEY.asc</tt></i>'</tt></b>
</pre><p>
@@ -72,33 +74,33 @@
use this command:
</p><pre class="screen">
<b class="userinput"><tt>su -c 'rpm --import <i class="replaceable"><tt>http://www.therepository.com/GPG-PUB-KEY.asc</tt></i>'</tt></b>
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-compat-repositories"></a>7.3. Understanding Repository Compatibility</h3></div></div><div></div></div><a class="indexterm" name="id2830751"></a><a class="indexterm" name="id2830763"></a><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-compat-repositories"></a>7.3. Understanding Repository Compatibility</h3></div></div><div></div></div><a class="indexterm" name="id2839068"></a><a class="indexterm" name="id2839080"></a><p>
The Fedora Extras project provides packages which are built to the same
- standards as Fedora Core packages. Third-party packages should be
- compatible with these official packages, unless the provider
- specifically states otherwise.
+ standards as Fedora Core packages. Third-party packages should be
+ compatible with these official packages, unless the provider
+ specifically states otherwise.
</p><p>
Refer to the web site of the repository for information on
- package compatibility before you add it as a package source.
- Repositories often provide packages specifically intended for
- use with packages supplied by other repositories. In some cases,
- separate third-party repository providers may each offer
- different versions of the same software. This situation may
- prevent you from safely using those repositories together on
- your Fedora system.
+ package compatibility before you add it as a package source.
+ Repositories often provide packages specifically intended for
+ use with packages supplied by other repositories. In some cases,
+ separate third-party repository providers may each offer
+ different versions of the same software. This situation may
+ prevent you from safely using those repositories together on
+ your Fedora system.
</p><p>
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.
+ compatible with other versions of Fedora. The web site of the
+ provider should specifically state which versions of Fedora they
+ support.
</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Old Versions of yum and Current Repositories"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="./stylesheet-images/tip.png"></td><th align="left">Old Versions of yum and Current Repositories</th></tr><tr><td colspan="2" align="left" valign="top"><p>
The data format for repository indexes changed with version
- 2.1 of <tt class="command">yum</tt>. This was the version supplied
- with Fedora 3. Repository providers should specify the versions
- of Fedora that they support. To confirm that an unlabeled
- repository is compatible with current versions of
- <tt class="command">yum</tt>, check that it has a sub-directory
- called <tt class="filename">repodata/</tt>.
+ 2.1 of <tt class="command">yum</tt>. This was the version supplied
+ with Fedora 3. Repository providers should specify the versions
+ of Fedora that they support. To confirm that an unlabeled
+ repository is compatible with current versions of
+ <tt class="command">yum</tt>, check that it has a sub-directory
+ called <tt class="filename">repodata/</tt>.
</p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-updating-your-system.php">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.php">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sn-yum-maintenance.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6. Updating Your System with yum </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 8. Maintaining yum</td></tr></table></div>
<?
Index: sn-yum-installing-frompackage.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/sn-yum-installing-frompackage.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-yum-installing-frompackage.php 25 Jul 2005 19:12:46 -0000 1.1
+++ sn-yum-installing-frompackage.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -7,7 +7,7 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">9. Manually Installing Software</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-yum-maintenance.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-yum-proxy-server.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-yum-installing-frompackage"></a>9. Manually Installing Software</h2></div></div><div></div></div><a class="indexterm" name="id2766291"></a><a class="indexterm" name="id2831320"></a><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">9. Manually Installing Software</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-yum-maintenance.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="sn-yum-proxy-server.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-yum-installing-frompackage"></a>9. Manually Installing Software</h2></div></div><div></div></div><a class="indexterm" name="id2839488"></a><a class="indexterm" name="id2839505"></a><p>
Use repositories and the standard <tt class="command">yum</tt> commands
to install new software, unless the software is only available as
a package. In these cases, use the <tt class="option">localinstall</tt>
@@ -24,7 +24,8 @@
</p><pre class="screen">
<b class="userinput"><tt>su -c 'yum localinstall <i class="replaceable"><tt>tsclient-0.132-4.i386.rpm</tt></i>'</tt></b>
</pre><p>
- At the prompt, enter the <tt class="systemitem">root</tt> password.
+ At the prompt, enter the
+ <tt class="systemitem">root</tt> password.
</p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Meeting Dependencies"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="./stylesheet-images/important.png"></td><th align="left">Meeting Dependencies</th></tr><tr><td colspan="2" align="left" valign="top"><p>
You must ensure that all of the dependencies are already
installed on your system, because <tt class="command">yum</tt> cannot
Index: sn-yum-maintenance.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/sn-yum-maintenance.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-yum-maintenance.php 25 Jul 2005 19:12:46 -0000 1.1
+++ sn-yum-maintenance.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -14,24 +14,24 @@
definitions which you no longer require. You may also clear the
files from the <tt class="command">yum</tt> caches in order to recover
disk space.
- </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-removing-sources"></a>8.1. Disabling or Removing Package Sources</h3></div></div><div></div></div><a class="indexterm" name="id2830892"></a><a class="indexterm" name="id2830904"></a><p>
+ </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-removing-sources"></a>8.1. Disabling or Removing Package Sources</h3></div></div><div></div></div><a class="indexterm" name="id2839213"></a><a class="indexterm" name="id2839225"></a><p>
Set <tt class="command">enable=0</tt> in a definition file to prevent
- <tt class="command">yum</tt> from using that repository. The
- <tt class="command">yum</tt> utility ignores any definition file with
- this setting.
+ <tt class="command">yum</tt> from using that repository. The
+ <tt class="command">yum</tt> utility ignores any definition file with
+ this setting.
</p><p>
To completely remove access to a repository:
</p><div class="procedure"><ol type="1"><li><p>
Delete the relevant file from
- <tt class="filename">/etc/yum.repos.d/</tt>.
+ <tt class="filename">/etc/yum.repos.d/</tt>.
</p></li><li><p>
Delete the cache directory from
- <tt class="filename">/var/cache/yum/</tt>.
- </p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-clearance"></a>8.2. Clearing the <tt class="command">yum</tt> Caches</h3></div></div><div></div></div><a class="indexterm" name="id2831027"></a><p>
+ <tt class="filename">/var/cache/yum/</tt>.
+ </p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="sn-yum-clearance"></a>8.2. Clearing the <tt class="command">yum</tt> Caches</h3></div></div><div></div></div><a class="indexterm" name="id2839346"></a><p>
By design, <tt class="command">yum</tt> does not automatically delete
- any of the packages or package data files it downloads, so they
- may be reused in future operations. To purge the header files,
- use this command:
+ any of the packages or package data files it downloads, so they
+ may be reused in future operations. To purge the header files,
+ use this command:
</p><pre class="screen">
<b class="userinput"><tt>su -c 'yum clean headers'</tt></b>
</pre><p>
@@ -41,11 +41,11 @@
<b class="userinput"><tt>su -c 'yum clean packages'</tt></b>
</pre><p>
When using these commands, at the prompt, enter the password for
- the <tt class="systemitem">root</tt> account.
+ the <tt class="systemitem">root</tt> account.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Purged Files"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Purged Files</th></tr><tr><td colspan="2" align="left" valign="top"><p>
Package management operations download header files and
- packages as required, and automatically replace any deleted
- files needed for the operation.
+ packages as required, and automatically replace any deleted
+ files needed for the operation.
</p></td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-using-repositories.php">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.php">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="sn-yum-installing-frompackage.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">7. Using Other Software Repositories </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> 9. Manually Installing Software</td></tr></table></div>
<?
Index: sn-yum-proxy-server.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/beta/yum-software-management/sn-yum-proxy-server.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sn-yum-proxy-server.php 25 Jul 2005 19:12:46 -0000 1.1
+++ sn-yum-proxy-server.php 26 Jul 2005 01:42:03 -0000 1.2
@@ -7,21 +7,22 @@
?>
-<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">10. Using yum with a Proxy Server</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-yum-installing-frompackage.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="generated-index.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-yum-proxy-server"></a>10. Using <tt class="command">yum</tt> with a Proxy Server</h2></div></div><div></div></div><a class="indexterm" name="id2831452"></a><a class="indexterm" name="id2831460"></a><p>
+<div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">10. Using yum with a Proxy Server</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sn-yum-installing-frompackage.php">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="generated-index.php">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sn-yum-proxy-server"></a>10. Using <tt class="command">yum</tt> with a Proxy Server</h2></div></div><div></div></div><a class="indexterm" name="id2839637"></a><a class="indexterm" name="id2839646"></a><p>
You may access repositories through standard web proxy servers. If
your system is connected to the Internet through a web proxy
server, specify the proxy server details in
<tt class="filename">/etc/yum.conf</tt>. The <tt class="option">proxy</tt>
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
- <tt class="option">proxy_username</tt> and
- <tt class="option">proxy_password</tt> settings.
+ password, specify these by adding <tt class="option">proxy_username</tt>
+ and <tt class="option">proxy_password</tt> settings.
</p><p>
The settings below enable <tt class="command">yum</tt> to use the proxy
- server <tt class="systemitem">mycache.mydomain.com</tt>, connecting
- to port 3128, with the username <tt class="systemitem">yum-user</tt> and the password
- <tt class="systemitem">qwerty</tt>.
+ server
+ <tt class="systemitem">mycache.mydomain.com</tt>,
+ connecting to port 3128, with the username
+ <tt class="systemitem">yum-user</tt> and the
+ password <tt class="systemitem">qwerty</tt>.
</p><div class="example"><a name="config-file-httpproxy"></a><pre class="screen">
<tt class="computeroutput"># The proxy server - proxy server:port number
proxy=http://mycache.mydomain.com:3128
@@ -30,16 +31,17 @@
proxy_password=qwerty</tt>
</pre><p class="title"><b>Example 2. Configuration File Settings for Using A Proxy Server</b></p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Global Settings"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">Global Settings</th></tr><tr><td colspan="2" align="left" valign="top"><p>
If you define a proxy server in
- <tt class="filename">/etc/yum.conf</tt>, <span class="emphasis"><em>all</em></span>
- users connect to the proxy server with those details when using
- <tt class="command">yum</tt>.
+ <tt class="filename">/etc/yum.conf</tt>, <span class="emphasis"><em>all</em></span>
+ users connect to the proxy server with those details when using
+ <tt class="command">yum</tt>.
</p></td></tr></table></div><p>
To enable proxy access for a specific user, add the lines in the
example box below to the user's shell profile. For the default
<tt class="command">bash</tt> shell, the profile is the file
<tt class="filename">~/.bash_profile</tt>. The settings below enable
- <tt class="command">yum</tt> to use the proxy server <tt class="systemitem">mycache.mydomain.com</tt>, connecting
- to port 3128.
+ <tt class="command">yum</tt> to use the proxy server
+ <tt class="systemitem">mycache.mydomain.com</tt>,
+ connecting to port 3128.
</p><div class="example"><a name="profile-script-httpproxy"></a><pre class="screen">
<tt class="computeroutput"># The Web proxy server used by this account
http_proxy="http://mycache.mydomain.com:3128"
@@ -47,21 +49,19 @@
</pre><p class="title"><b>Example 3. Profile Settings for Using a Proxy Server</b></p></div><p>
If the proxy server requires a username and password, add these to
the URL. To include the username
- <tt class="systemitem">yum-user</tt> and the password
- <tt class="systemitem">qwerty</tt>, add these settings:
+ <tt class="systemitem">yum-user</tt> and the
+ password <tt class="systemitem">qwerty</tt>, add these settings:
</p><div class="example"><a name="profile-script-httpproxy-withpassword"></a><pre class="screen">
<tt class="computeroutput"># 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</tt>
-</pre><p class="title"><b>Example 4. Profile Settings for a Secured Proxy Server</b></p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: The http_proxy Environment
- Variable"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">The http_proxy Environment
- Variable</th></tr><tr><td colspan="2" align="left" valign="top"><p>
+</pre><p class="title"><b>Example 4. Profile Settings for a Secured Proxy Server</b></p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: The http_proxy Environment Variable"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="./stylesheet-images/note.png"></td><th align="left">The http_proxy Environment Variable</th></tr><tr><td colspan="2" align="left" valign="top"><p>
The <tt class="command">http_proxy</tt> environment variable is also
- used by <tt class="command">curl</tt> and other utilities. Although
- <tt class="command">yum</tt> itself may use
- <tt class="command">http_proxy</tt> in either upper-case or
- lower-case, <tt class="command">curl</tt> requires the name of the
- variable to be in lower-case.
+ used by <tt class="command">curl</tt> and other utilities. Although
+ <tt class="command">yum</tt> itself may use
+ <tt class="command">http_proxy</tt> in either upper-case or
+ lower-case, <tt class="command">curl</tt> requires the name of the
+ variable to be in lower-case.
</p></td></tr></table></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sn-yum-installing-frompackage.php">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.php">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="generated-index.php">Next</a></td></tr><tr><td width="40%" align="left" valign="top">9. Manually Installing Software </td><td width="20%" align="center"><a accesskey="h" href="index.php">Home</a></td><td width="40%" align="right" valign="top"> Index</td></tr></table></div>
<?
More information about the fedora-extras-commits
mailing list