yum-software-management yum-software-management-en.xml,1.29,1.30
Stuart Ellis (elliss)
fedora-docs-commits at redhat.com
Wed Jul 27 21:27:34 UTC 2005
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2737
Modified Files:
yum-software-management-en.xml
Log Message:
- Revised section on Repository Compatibility.
- Style fix in Advanced Search section.
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- yum-software-management-en.xml 26 Jul 2005 23:29:18 -0000 1.29
+++ yum-software-management-en.xml 27 Jul 2005 21:27:32 -0000 1.30
@@ -679,7 +679,7 @@
<tip>
<title>Downloads are Cached</title>
<para>
- The <command>yum</command> utility keeps Downloaded data files
+ The <command>yum</command> utility keeps downloaded data files
and packages for reuse. You may copy packages from the
repository cache directories under
<filename>/var/cache/yum/</filename>, and use them elsewhere if
@@ -915,6 +915,8 @@
<para>
If you do not know the name of the package, use the
<option>search</option> or <option>provides</option> options.
+ Alternatively, you may use wild cards and regular expressions
+ with any <command>yum</command> search option.
</para>
<para>
@@ -962,8 +964,8 @@
<para>
Use the standard wildcard characters to run any search option
- without a complete name: <option>?</option> to represent any one
- character, and <option>*</option> to mean zero or more
+ with a partial word or name: <option>?</option> to represent any
+ one character, and <option>*</option> to mean zero or more
characters. Always add the escape character (<option>\</option>)
before wildcards.
</para>
@@ -1207,23 +1209,31 @@
<secondary>compatibility</secondary>
</indexterm>
<para>
- The &FEX; project provides packages which are built to the same
- standards as &FC; packages. Third-party packages should be
- compatible with these official packages, unless the provider
+ The &FEX; repository provides packages which are built to the
+ same standards as &FC; packages. Third-party packages should be
+ compatible with these &FP; packages, unless the provider
specifically states otherwise.
</para>
<para>
- Refer to the web site of the repository for information on
+ Always read 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 &FED; system.
+ Separate repository providers may offer different and
+ incompatible versions of the same software. In some cases,
+ third-party repositories may also include alternative packages
+ for software provided by &FP; repositories that are not
+ compatible with other &FED; packages.
</para>
+ <caution>
+ <title>Incompatible Repositories</title>
+
+ <para>
+ If you use incompatible repositories <command>yum</command>
+ operations may fail.
+ </para>
+ </caution>
+
<para>
Packages built for one version of &FED; are usually not
compatible with other versions of &FED;. The web site of the
@@ -1381,10 +1391,10 @@
<secondary>cleaning caches</secondary>
</indexterm>
<para>
- By default, <command>yum</command> retains the packages or
+ By default, <command>yum</command> retains the packages and
package data files that it downloads, so they may be reused in
future operations without being downloaded again. To purge the
- header files, use this command:
+ package data files, use this command:
</para>
<screen>
<userinput>su -c 'yum clean headers'</userinput>
More information about the docs-commits
mailing list