yum-software-management yum-software-management-en.xml,1.28,1.29

Stuart Ellis (elliss) fedora-docs-commits at redhat.com
Tue Jul 26 23:29:21 UTC 2005


Author: elliss

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

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

- Clarify wording on effect of purging caches  
- Explicitly list Fedora repositories
- Amended explanation of use of wildcards in searches



Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- yum-software-management-en.xml	25 Jul 2005 21:57:58 -0000	1.28
+++ yum-software-management-en.xml	26 Jul 2005 23:29:18 -0000	1.29
@@ -261,13 +261,27 @@
 
       <para>
         The package management utilities in &FC; are already configured
-        to use the network of repositories maintained by the &FP;. These
-        repositories contain the software included with &FC; and a large
-        selection of additional software known as &FEX;. Third-party
-        software developers also provide repositories for their &FED;
-        compatible packages.
+        to use a network of servers that provide three repositories:
       </para>
 
+      <itemizedlist>
+        <listitem>
+          <para>
+            The packages that make up &FC;, as it is released on disc
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            Updated versions of &FC; software
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            A large selection of additional software, known as &FEX;
+          </para>
+        </listitem>
+      </itemizedlist>
+
       <note>
         <title>All &FED; Packages are Open Source Software</title>
 
@@ -277,6 +291,13 @@
           network of repositories on as many systems as desired.
         </para>
       </note>
+
+      <para>
+        Third-party software developers also provide repositories for
+        their &FED; compatible packages. To learn how to configure your
+        &FED; system to use third-party repositories, read
+        <xref linkend="sn-using-repositories"/>.
+      </para>
       <indexterm>
         <primary>package groups</primary>
         <secondary>defined</secondary>
@@ -373,8 +394,8 @@
 <filename>tsclient-0.132-4.i386.rpm</filename>
 </screen>
       <para>
-        Management utilities refer to packages with one of three
-        formats:
+        Management utilities commonly refer to packages with one of
+        three formats:
       </para>
 
       <itemizedlist>
@@ -603,18 +624,11 @@
     </para>
 
     <para>
-      <command>yum</command> 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.
-    </para>
-
-    <para>
       During operation, <command>yum</command> first determines the best
       set of actions to produce the required result, and displays the
       transaction for you to approve. The <command>yum</command> utility
-      may prompt you to approve installation, update, or removal of
-      additional packages in addition to the package that you specified.
-      These actions may be necessary to resolve software dependencies.
+      may prompt you to approve the installation, update, or removal of
+      additional packages, in order to resolve software dependencies.
     </para>
 
     <example id="yum-transaction-format">
@@ -877,20 +891,29 @@
       </para>
 
       <para>
-        To make your queries more specific, add other package
-        attributes. To search for version 0.132 of the application, use
-        the command:
+        To make your queries more precise, specify packages with a name
+        that include other attributes, such as version or hardware
+        architecture. To search for version 0.132 of the application,
+        use the command:
       </para>
 <screen>
 <userinput>su -c 'yum list <replaceable>tsclient-0.132</replaceable>'</userinput>
 </screen>
+      <note>
+        <title>Valid Package Attributes</title>
+
+        <para>
+          Refer to <xref linkend="sn-package-names" /> for information
+          on package name formats and the attributes that they include.
+        </para>
+      </note>
     </section>
 
     <section id="sn-searching-packages-advanced">
       <title>Advanced Searches</title>
 
       <para>
-        If you do not know the name of the package, use either the
+        If you do not know the name of the package, use the
         <option>search</option> or <option>provides</option> options.
       </para>
 
@@ -936,14 +959,27 @@
         For each command, at the prompt enter the password for the
         <systemitem class="username">root</systemitem> account.
       </para>
+
+      <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
+        characters. Always add the escape character (<option>\</option>)
+        before wildcards.
+      </para>
+
+      <para>
+        To <option>list</option> all packages with names that begin with
+        <filename>tsc</filename>, type:
+      </para>
+<screen>
+<userinput>su -c 'yum list <replaceable>tsc\*</replaceable>'</userinput>
+</screen>
       <tip>
-        <title>Wildcards and Regular Expressions</title>
+        <title>Regular Expressions</title>
         <para>
-          You may use the standard wildcard characters in search
-          criteria: <option>?</option> to represent any one character,
-          and <option>*</option> to mean zero or more characters. Use
-          Perl or Python regular expressions to carry out more complex
-          queries.
+          Use Perl or Python regular expressions to carry out more
+          complex queries.
         </para>
       </tip>
     </section>
@@ -963,8 +999,8 @@
         or <filename>shadow-util</filename> would not produce the
         package <filename>shadow-utils</filename>. This package would
         match and be shown if the query was either
-        <filename>shadow-util?</filename> or
-        <filename>Shadow*</filename>.
+        <filename>shadow-util\?</filename> or
+        <filename>Shadow\*</filename>.
       </para>
     </section>
   </section>
@@ -1345,10 +1381,10 @@
         <secondary>cleaning caches</secondary>
       </indexterm>
       <para>
-        By design, <command>yum</command> 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:
+        By default, <command>yum</command> retains the packages or
+        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:
       </para>
 <screen>
 <userinput>su -c 'yum clean headers'</userinput>
@@ -1365,15 +1401,11 @@
         the <systemitem class="username">root</systemitem> account.
       </para>
 
-      <note>
-        <title>Purged Files</title>
-
-        <para>
-          Package management operations download header files and
-          packages as required, and automatically replace any deleted
-          files needed for the operation.
-        </para>
-      </note>
+      <para>
+        Purging cached files causes those files to downloaded again the
+        next time that they are required. This increases the amount of
+        time required to complete the operation.
+      </para>
     </section>
   </section>
 




More information about the docs-commits mailing list