yum-software-management/en_US concepts.xml, 1.8, 1.9 introduction.xml, 1.4, 1.5 rpm-info.xml, 1.2, 1.3 tools.xml, 1.3, 1.4
Jared Smith (jsmith)
fedora-docs-commits at redhat.com
Thu Feb 14 12:15:13 UTC 2008
Author: jsmith
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27073
Modified Files:
concepts.xml introduction.xml rpm-info.xml tools.xml
Log Message:
A round of general edits that I forgot to check in last week.
Index: concepts.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/concepts.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- concepts.xml 24 Jan 2008 01:48:01 -0000 1.8
+++ concepts.xml 14 Feb 2008 12:15:10 -0000 1.9
@@ -25,9 +25,9 @@
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
+ <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>
@@ -41,10 +41,10 @@
<section id="sn-AboutRepositories">
<title>About Repositories</title>
<para>A
- <firstterm>repository</firstterm>is a prepared directory or Web
+ <firstterm>repository</firstterm> is a prepared directory or Web
site that contains software packages and index files. Software
management utilities such as
- <package>yum</package>automatically locate and obtain the correct
+ <package>yum</package> 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
@@ -80,7 +80,7 @@
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-devel</systemitem> (Rawhide),
<systemitem>fedora-extras-devel</systemitem>, and
<systemitem>updates-testing</systemitem>.</para>
</warning>
@@ -89,16 +89,16 @@
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
+ <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>
+ <tip>
<title>Available Package Groups</title>
<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>
+ </tip>
<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
@@ -111,36 +111,36 @@
of with Fedora software management utilities.</para>
</warning>
<para>The
- <command>yum</command>commands shown in this document use
+ <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
+ <command>yum</command> to install software from a package
file.</para>
<para />
</section>
<section id="sn-AboutDependencies">
<title>About Dependencies</title>
<para>Some of the files installed on a Fedora distribution are
- <firstterm>libraries</firstterm>which may provide functions to
+ <firstterm>libraries</firstterm> which may provide functions to
multiple applications. When an application requires a specific
library, the package which contains that library is a
<firstterm>dependency</firstterm>. 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
- <application>yum</application>utility uses package dependency data
+ <application>yum</application> 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,
- <application>yum</application>aborts without making any changes to
+ <application>yum</application> aborts without making any changes to
your system.</para>
</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
- <package>tsclient</package>package:</para>
+ <package>tsclient</package> package:</para>
<para>
<filename>tsclient-0.132-6.i386.rpm</filename>
</para>
@@ -149,23 +149,23 @@
<itemizedlist>
<listitem>
<para>Package name:
- <package>tsclient</package></para>
+ <literal>tsclient</literal></para>
</listitem>
<listitem>
<para>Package name with version and release numbers:
- <package>tsclient-0.132-6</package></para>
+ <literal>tsclient-0.132-6</literal></para>
</listitem>
<listitem>
<para>Package name with hardware architecture:
- <package>tsclient.i386</package></para>
+ <literal>tsclient.i386</literal></para>
</listitem>
</itemizedlist>
<para>For clarity,
- <command>yum</command>lists packages in the format
+ <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
+ <emphasis>minimum</emphasis> type of machine required to use the
package.</para>
<segmentedlist>
<segtitle>Architecture</segtitle>
@@ -193,36 +193,36 @@
Intel-compatible machine. Separate packages may be provided for
<systemitem>i386</systemitem>,
<systemitem>i586</systemitem>,
- <systemitem>i686</systemitem>and
- <systemitem>x86_64</systemitem>computers. A machine with at least
+ <systemitem>i686</systemitem> and
+ <systemitem>x86_64</systemitem> computers. A machine with at least
an Intel Pentium, VIA C3 or compatible CPU may use
- <systemitem>i586</systemitem>packages. Computers with an Intel
+ <systemitem>i586</systemitem> packages. Computers with an Intel
Pentium Pro and above, or a current model of AMD chip, may use
- <systemitem>i686</systemitem>packages.</para>
+ <systemitem>i686</systemitem> packages.</para>
<para>Use the short name of the package for
- <command>yum</command>commands. This causes
- <command>yum</command>to automatically select the most recent
+ <command>yum</command> commands. This causes
+ <command>yum</command> 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
- <command>yum</command>to use the package that matches that version
+ <command>yum</command> to use the package that matches that version
or architecture. Only override
- <command>yum</command>when you know that the default package
+ <command>yum</command> 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
- <command>yum</command>operation:
- <package>name</package>,
- <package>name.architecture</package>,
- <package>name-version</package>,
- <package>name-version-release</package>,
- <package>name-version-release.architecture</package>, and
- <package>
- epoch:name-version-release.architecture</package>.</para>
+ <application>yum</application> operation:
+ <literal>name</literal>,
+ <literal>name.architecture</literal>,
+ <literal>name-version</literal>,
+ <literal>name-version-release</literal>,
+ <literal>name-version-release.architecture</literal>, and
+ <literal>
+ epoch:name-version-release.architecture</literal>.</para>
</important>
</section>
</section>
Index: introduction.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/introduction.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- introduction.xml 24 Jan 2008 01:48:01 -0000 1.4
+++ introduction.xml 14 Feb 2008 12:15:10 -0000 1.5
@@ -13,31 +13,34 @@
<section id="sn-AboutDocument">
<title>About this Document</title>
<para>
- <emphasis role="strong">Purpose</emphasis>: How to install and update software
- packages from the desktop and the CLI.</para>
+ <emphasis role="strong">Purpose</emphasis>: This document will
+ demonstrate how to install and update software
+ packages from the desktop and the Linux command-line.</para>
<para>
- <emphasis role="strong">Audience</emphasis>: Individuals who are unfamiliar with
+ <emphasis role="strong">Audience</emphasis>: This document was
+ written for individuals who are unfamiliar with
software package management in Fedora.</para>
<para>
- <emphasis role="strong">Approach</emphasis>: Explain basic principles; explain
- one principle at a time; do not assume familiarity with any
- Linux/UNIX-specific terminology or concepts; compare functionality
+ <emphasis role="strong">Approach</emphasis>: This document will explain
+ basic principles, one at a time, and will not assume familiarity with any
+ Linux/UNIX-specific terminology or concepts. It will compare functionality
where appropriate to what the reader may know from other operating
- systems, particularly Microsoft Windows.</para>
+ systems.</para>
<para>
- <emphasis role="strong">Assumptions</emphasis>: The reader has a default
+ <emphasis role="strong">Assumptions</emphasis>: This document
+ assumes that the reader has a default
installation of Fedora which includes the desktop components. The
- reader has a user account with the default settings. The reader
- <emphasis role="strong">does</emphasis> have access to the
- <systemitem class="username">root</systemitem> password. The user does not have a degree
- in Computer Science.</para>
+ reader must have a user account with the default settings. The reader
+ <emphasis role="strong">does</emphasis> must have access to the
+ <systemitem class="username">root</systemitem> password.
+ </para>
</section>
<section id="sn-UsingDocument">
<title>Using This Document</title>
<para>This document is a reference for managing software with
Fedora. You may wish to read some or all of the sections, depending
upon your needs and level of experience. If you are a new user,
- start with:</para>
+ please start with:</para>
<itemizedlist>
<listitem>
<para>
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/rpm-info.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-info.xml 24 Jan 2008 20:06:50 -0000 1.2
+++ rpm-info.xml 14 Feb 2008 12:15:10 -0000 1.3
@@ -29,7 +29,7 @@
<desc>Documentation for the yum software management system.</desc>
<changelog order="newest-first">
<revision date="2008-01-24" number="2.01" role="doc">
- <author worker="Jared Smith"/>
+ <author worker="JaredKSmith"/>
<details>Import new version from Wiki, convert to DocBook.</details>
</revision>
<revision date="2006-04-30" number="1.31" role="doc">
Index: tools.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/tools.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- tools.xml 24 Jan 2008 01:48:01 -0000 1.3
+++ tools.xml 14 Feb 2008 12:15:10 -0000 1.4
@@ -59,6 +59,10 @@
version of software packages. Other methods do not guarantee that
the packages are current.</para>
</warning>
+ <para>For more information on <application>pup</application>, see
+ <xref linkend="sn-Pup"/>. For more information on
+ <application>pirut</application>, see <xref linkend="sn-Pirut"/>.
+ </para>
</section>
<!--
Local variables:
More information about the Fedora-docs-commits
mailing list