yum-software-management/en_US concepts.xml,1.3,1.4

Paul W. Frields (pfrields) fedora-docs-commits at redhat.com
Tue Jan 22 02:56:18 UTC 2008


Author: pfrields

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

Modified Files:
	concepts.xml 
Log Message:
Fix some tagging, work continues



Index: concepts.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/concepts.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- concepts.xml	22 Jan 2008 02:52:15 -0000	1.3
+++ concepts.xml	22 Jan 2008 02:56:16 -0000	1.4
@@ -9,48 +9,98 @@
 ]>
   <section id="sn-Concepts">
     <title>Software Management Concepts</title>
-    <para/>
   <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>
+    <para>Fedora software and documentation is supplied in the form of
+      files called RPM <firstterm>packages</firstterm>. 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 <firstterm>public key</firstterm>. The
+      <command>yum</command> and <command>rpm</command> utilities share a common
+      <firstterm>keyring</firstterm> that stores all of the public keys
+      for approved package sources. The system administrator configures
+      these approved package sources. </para>
     <note>
-      <title>All Fedora Packages are Free and Open Source Software</title>
-      <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>
+      <title>All Fedora Packages are Free and Open Source
+	Software</title>
+      <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 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>
+    <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>
     <para>Base </para>
     <itemizedlist>
-      <listitem><para>The packages that make up a Fedora release, as it is on disc  </para></listitem>
+      <listitem><para>The packages that make up a Fedora release, as it
+	  is on disc  </para></listitem>
     </itemizedlist>
     <para>Updates </para>
     <itemizedlist>
-      <listitem><para>Updated versions of packages that are provided in Base  </para></listitem>
+      <listitem><para>Updated versions of packages that are provided in
+	  Base  </para></listitem>
     </itemizedlist>
     <para>Extras </para>
     <itemizedlist>
-      <listitem><para>Packages for a large selection of additional software  </para></listitem>
+      <listitem><para>Packages for a large selection of additional
+	  software  </para></listitem>
     </itemizedlist>
     <warning>
-	   <title>Fedora Development Repositories</title>
-      <para> Fedora also includes settings for several alternative repositories. These provide packages for various types of test system, and replace one or more of the standard repositories. Only enable support for one of the following repositories if you test or develop Fedora software: <code>fedora-devel</code> (Rawhide), <code>fedora-extras-devel</code>, and <code>updates-testing</code>. </para>
+      <title>Fedora Development Repositories</title>
+      <para> Fedora also includes settings for several alternative
+	repositories. These provide packages for various types of test
+	system, and replace one or more of the standard repositories.
+	Only enable support for one of the following repositories if you
+	test or develop Fedora software: <systemitem>fedora-devel</systemitem>
+	(Rawhide), <systemitem>fedora-extras-devel</systemitem>, and
+	<systemitem>updates-testing</systemitem>. </para>
     </warning>
-      <para>Third-party software developers also provide repositories for their Fedora compatible packages. To learn how to configure your Fedora system to use third-party repositories, read <xref linkend="sn-ConfiguringRepositories"/>. </para>
-    <para>You may also use the <emphasis>package groups</emphasis> 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. </para>
+    <para>Third-party software developers also provide repositories for
+      their Fedora compatible packages. To learn how to configure your
+      Fedora system to use third-party repositories, read <xref
+	linkend="sn-ConfiguringRepositories"/>. </para>
+    <para>You may also use the <firstterm>package groups</firstterm>
+      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. </para>
     <important>
       <title>Available Package Groups</title>
-              <para> To view a list of all of the available package groups for your Fedora system, run the command <code>su -c 'yum grouplist'</code>. </para>
+      <para> To view a list of all of the available package groups for
+	your Fedora system, run the command <command>su -c 'yum
+	  grouplist'</command>. </para>
     </important>
-    <para>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. </para>
+    <para>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. </para>
     <warning>
       <title>Manually Installing Software</title>
-      <para> 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. </para>
+      <para> 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. </para>
     </warning>
-    <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>The <command>yum</command> commands shown in this document use
+      repositories as package sources. Refer to  <xref
+	linkend="sn-IsolatedInstall"/> for details of using
+      <command>yum</command> to install software from a package file. </para>
     <para/>
   </section>
   <section id="sn-AboutDependencies">
@@ -60,45 +110,81 @@
   </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>Each package file has a long name that indicates several key
+      pieces of information. For example, this is the full name of a
+      <package>tsclient</package> package: </para>
     <para>
-      <code>tsclient-0.132-6.i386.rpm</code>
+      <filename>tsclient-0.132-6.i386.rpm</filename>
     </para>
-    <para>Management utilities commonly refer to packages with one of three formats: </para>
+    <para>Management utilities commonly refer to packages with one of
+      three formats: </para>
     <itemizedlist>
       <listitem>
-        <para>Package name: <code>tsclient</code> </para>
+        <para>Package name: <package>tsclient</package> </para>
       </listitem>
       <listitem>
-        <para>Package name with version and release numbers: <code>tsclient-0.132-6</code> </para>
+        <para>Package name with version and release numbers:
+	  <package>tsclient-0.132-6</package> </para>
       </listitem>
       <listitem>
-        <para>Package name with hardware architecture: <code>tsclient.i386</code>  </para>
+        <para>Package name with hardware architecture:
+	  <package>tsclient.i386</package>  </para>
       </listitem>
     </itemizedlist>
-    <para>For clarity, <code>yum</code> lists packages in the format <code>name.architecture</code>. 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>
-    <para>i386 </para>
-    <itemizedlist>
-      <listitem><para>Suitable for any current Intel-compatible computer  </para></listitem>
-    </itemizedlist>
-    <para>noarch </para>
-    <itemizedlist>
-      <listitem><para>Compatible with all computer architectures  </para></listitem>
-    </itemizedlist>
-    <para>ppc </para>
-    <itemizedlist>
-      <listitem><para>Suitable for PowerPC systems, such as Apple Power Macintosh  </para></listitem>
-    </itemizedlist>
-    <para>x86_64 </para>
-    <itemizedlist>
-      <listitem><para>Suitable for 64-bit Intel-compatible processors, such as Opterons  </para></listitem>
-    </itemizedlist>
-    <para>Some software may be optimized for particular types of Intel-compatible machine. Separate packages may be provided for <code>i386</code>, <code>i586</code>, <code>i686</code> and <code>x86_64</code> computers. A machine with at least an Intel Pentium, VIA C3 or compatible CPU may use <code>i586</code> packages. Computers with an Intel Pentium Pro and above, or a current model of AMD chip, may use <code>i686</code> packages. </para>
-    <para>Use the short name of the package for <code>yum</code> commands. This causes <code>yum</code> to automatically select the most recent package in the repositories that matches the hardware architecture of your computer. </para>
-    <para>Specify a package with other name formats to override the default behavior and force <code>yum</code> to use the package that matches that version or architecture. Only override <code>yum</code> when you know that the default package selection has a bug or other fault that makes it unsuitable for installation. </para>
+    <para>For clarity, <command>yum</command> lists packages in the
+      format <package>name.architecture</package>. 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>
+    <segmentedlist>
+      <segtitle>Architecture</segtitle>
+      <segtitle>Compatibility</segtitle>
+      <seglistitem>
+	<seg>i386</seg>
+	<seg>Suitable for any current Intel-compatible computer</seg>
+      </seglistitem>
+      <seglistitem>
+	<seg>noarch </seg>
+	<seg>Compatible with all computer architectures
+	</seg>
+      </seglistitem>
+      <seglistitem>
+	<seg>ppc </seg>
+	<seg>Suitable for PowerPC systems, such as Apple Power Macintosh
+	</seg>
+      </seglistitem>
+      <seglistitem>
+	<seg>x86_64 </seg>
+	<seg>Suitable for 64-bit Intel-compatible processors, such as
+	  Opterons  </seg>
+      </seglistitem>
+    </segmentedlist>
+    <para>Some software may be optimized for particular types of
+      Intel-compatible machine. Separate packages may be provided for
+      <code>i386</code>, <code>i586</code>, <code>i686</code> and
+      <code>x86_64</code> computers. A machine with at least an Intel
+      Pentium, VIA C3 or compatible CPU may use <code>i586</code>
+      packages. Computers with an Intel Pentium Pro and above, or a
+      current model of AMD chip, may use <code>i686</code> packages.
+    </para>
+    <para>Use the short name of the package for <code>yum</code>
+      commands. This causes <code>yum</code> to automatically select the
+      most recent package in the repositories that matches the hardware
+      architecture of your computer. </para>
+    <para>Specify a package with other name formats to override the
+      default behavior and force <code>yum</code> to use the package
+      that matches that version or architecture. Only override
+      <code>yum</code> when you know that the default package selection
+      has a bug or other fault that makes it unsuitable for
+      installation. </para>
     <important>
       <title>Package Names</title>
-      <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>
+      <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>




More information about the docs-commits mailing list