yum-software-management/en_US concepts.xml,1.1,1.2

[Jared Smith (jsmith)]

Author: jsmith

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

Modified Files:
	concepts.xml 
Log Message:
Add @id attributes for all sections



Index: concepts.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/concepts.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- concepts.xml	21 Jan 2008 22:21:19 -0000	1.1
+++ concepts.xml	22 Jan 2008 02:25:38 -0000	1.2
@@ -2,7 +2,7 @@
   <section id="sn-Concepts">
     <title>Software Management Concepts</title>
     <para/>
-  <section>
+  <section id="sn-AboutPackages">
     <title>About Packages</title>
     <para>Fedora software and documentation is supplied in the form of files called RPM <emphasis>packages</emphasis>. 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 to build or upgrade a system to your requirements. </para>
     <para>Packages also include a digital signature to prove their source. Software management utilities verify this digital signature by using a GPG <emphasis>public key</emphasis>. The <code>yum</code> and <code>rpm</code> utilities share a common <emphasis>keyring</emphasis> that stores all of the public keys for approved package sources. The system administrator configures these approved package sources. </para>
@@ -11,7 +11,7 @@
       <para> All of the software provided by the Fedora Project is Free and open source software. You may download and install Fedora packages on as many systems as desired. </para>
     </note>
   </section>
-  <section>
+  <section id="sn-AboutRepositories">
     <title>About Repositories</title>
     <para>A <emphasis>repository</emphasis> is a prepared directory or Web site that contains software packages and index files. Software management utilities such as <code>yum</code> 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 use a single command to update all system software, or search for new software by specifying criteria. </para>
     <para>A network of servers provide several repositories for each version of Fedora. The package management utilities in Fedora are already configured to use three of these repositories: </para>
@@ -45,7 +45,7 @@
     <para>The <code>yum</code> commands shown in this document use repositories as package sources. Refer to  <xref linkend="sn-IsolatedInstall"/> for details of using <code>yum</code> to install software from a package file. </para>
     <para/>
   </section>
-  <section>
+  <section id="sn-AboutDependencies">
     <title>About Dependencies</title>
     <para>Some of the files installed on a Fedora distribution are <emphasis>libraries</emphasis> which may provide functions to multiple applications. When an application requires a specific library, the package which contains that library is a <emphasis>dependency</emphasis>. To properly install a package, Fedora must first satisfy its dependencies. The dependency information for a RPM package is stored within the RPM file. </para>
     <para>The <code>yum</code> utility uses package dependency data 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, <code>yum</code> aborts without making any changes to your system. </para>
@@ -53,7 +53,7 @@
       <anchor id="understanding_package_names"/>
     </para>
   </section>
-  <section>
+  <section id="sn-UnderstandingPackageNames">
     <title>Understanding Package Names</title>
     <para>Each package file has a long name that indicates several key pieces of information. For example, this is the full name of a <code>tsclient</code> package: </para>
     <para>
@@ -96,4 +96,4 @@
       <para> You may use any of the following formats to specify a package in a <code>yum</code> operation: <code>name, name.architecture, name-version, name-version-release, name-version-release.architecture,</code> and <code>epoch:name-version-release.architecture</code>. </para>
     </important>
   </section>
-  </section>
+</section>