yum-software-management yum-software-management-en.xml,1.35,1.36

[Paul W. Frields (pfrields)]

Author: pfrields

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

Modified Files:
	yum-software-management-en.xml 
Log Message:
- Moved out of beta
- Removed draft notice
- Made correction to note about configuration file retention



Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- yum-software-management-en.xml	12 Aug 2005 13:24:55 -0000	1.35
+++ yum-software-management-en.xml	13 Aug 2005 21:36:31 -0000	1.36
@@ -17,8 +17,7 @@
 
 <article id="yum-software-management" lang="en">
   <articleinfo>
-    <title>Software Management with <command>yum</command> - <emphasis>BETA
-      DOCUMENT</emphasis></title>
+    <title>Software Management with <command>yum</command></title>
     <copyright>
       <year>2005</year>
       <holder>Stuart Ellis</holder>
@@ -61,12 +60,22 @@
           </para>
         </revdescription>
       </revision>
+      <revision>
+	<revnumber>1.0</revnumber>
+	<date>2005-08-13</date>
+	<authorinitials>PaulWFrields</authorinitials>
+	<revdescription>
+	  <para>
+	    Publish to official project page.
+	  </para>
+	</revdescription>
+      </revision>
     </revhistory>
   </articleinfo>
 
   <section id="sn-introduction">
     <title>Introduction</title>
-    &DRAFTNOTICE;
+
     <section id="sn-purpose">
       <title>Purpose</title>
 
@@ -443,12 +452,12 @@
       </itemizedlist>
 
       <para>
-        For clarity, <command>yum</command> itself lists packages in the
-        format <filename>name.architecture</filename>. Repositories also
-        commonly store packages in separate directories by architecture.
-        In each case, the hardware architecture specified for the
-        package is the <emphasis>minimum</emphasis> type of machine
-        required to use the package.
+        For clarity, <command>yum</command> lists packages in the format
+	<filename>name.architecture</filename>. Repositories also
+	commonly store packages in separate directories by architecture.
+	In each case, the hardware architecture specified for the
+	package is the <emphasis>minimum</emphasis> type of machine
+	required to use the package.
       </para>
 
       <variablelist>
@@ -716,15 +725,11 @@
         This is an example of the public key import:
       </para>
 <screen>
-<computeroutput>
-<![CDATA[
-warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
+<computeroutput>warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
 public key not available for tsclient-0.132-6.i386.rpm
 Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
 Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora at redhat.com>"
-Is this ok [y/N]:
-]]>
-</computeroutput>
+Is this ok [y/N]:</computeroutput>
 </screen>
     </example>
 
@@ -901,12 +906,13 @@
       </para>
 
       <note>
-        <title>Data and Settings are Retained</title>
+        <title>Data and Configuration File Retention</title>
 
         <para>
-          The removal process leaves configuration files and data in
-          place. If you reinstall removed software the new installation
-          uses the original configuration files.
+          The removal process leaves user data in place but may remove
+          configuration files in some cases.  If a package removal does
+          not include the configuration file, and you reinstall the
+          package later, it may reuse the old configuration file.
         </para>
       </note>
     </section>