yum-software-management yum-software-management-en.xml,1.23,1.24
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Mon Jul 25 02:12:48 UTC 2005
Author: pfrields
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1679
Modified Files:
yum-software-management-en.xml
Log Message:
A little further through the style wringer...
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- yum-software-management-en.xml 24 Jul 2005 17:28:24 -0000 1.23
+++ yum-software-management-en.xml 25 Jul 2005 02:12:45 -0000 1.24
@@ -207,15 +207,14 @@
<secondary>defined</secondary>
</indexterm>
<para>
- All of the software and documentation prepared for use with
- &FED; 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 &FED; installation process uses the
- packages supplied with &FC; to build or upgrade a system to your
- requirements.
+ &FED; 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 &FED; installation process
+ uses the packages supplied with &FC; to build or upgrade a
+ system to your requirements.
</para>
<para>
@@ -237,7 +236,7 @@
</indexterm>
<para>
A <firstterm>repository</firstterm> is a prepared directory or
- Website that contains software packages and index files.
+ web site that contains software packages and index files.
Software management utilities such as <command>yum</command>
automatically locate and obtain the correct RPM packages from
these repositories. This method frees you from having to
@@ -249,24 +248,23 @@
</para>
<para>
- The package management utilities in &FC; are automatically
- 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.
+ 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.
</para>
<note>
<title>All &FED; Packages are Open Source Software</title>
<para>
- All of the software provided by the &FP; is Open Source
- software, and can therefore be downloaded and installed
- from the network of &FED; repositories without restrictions.
+ All of the software provided by the &FP; is open source
+ software. You may download and install software from the &FP;
+ network of repositories on as many systems as desired.
</para>
</note>
-<!-- SE: The key point here is that users can install Fedora packages as many times as they like on as many systems as they like, as opposed to widely prevalent no-cost but not freely redistributable software -->
<indexterm>
<primary>package groups</primary>
<secondary>defined</secondary>
@@ -303,9 +301,8 @@
<para>
Install software using manual methods only when you are
confident there is no repository which can currently provide
- it. You may not be able to manage such software using &FED;
- software management utilities. You may need to update that
- software with manual methods.
+ it. You may have to manage that software with manual methods,
+ instead of with &FED; software management utilities.
</para>
<para>
The <command>yum</command> commands shown in this document use
@@ -367,8 +364,8 @@
</indexterm>
<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 supplied with &FC;:
+ pieces of information. This is the full name of the
+ <filename>tsclient</filename> package supplied with &FC;:
</para>
<screen>
<filename>tsclient-0.132-4.i386.rpm</filename>
@@ -385,8 +382,8 @@
</listitem>
<listitem>
<para>
- Package name with version number:
- <filename>tsclient-0.132-4</filename>
+ Package name with version and release numbers:
+ <filename>tsclient-0.132-4</filename>
</para>
<!-- In what instances is the release number not needed? For many -->
<!-- package updates, only the release number might change. Although it -->
@@ -395,7 +392,7 @@
<listitem>
<para>
Package name with hardware architecture:
- <filename>tsclient.i386</filename>
+ <filename>tsclient.i386</filename>
</para>
</listitem>
</itemizedlist>
@@ -413,6 +410,11 @@
computer for which the package is intended.
</para>
+<!-- I'm not sure we need any of this information on architecture. How -->
+<!-- exactly does this help a yum user? Note that I'm not being snide, -->
+<!-- I'm pointing out that unless this is hooked to a specific -->
+<!-- procedure, it's out of place in a tutorial. [PWF] -->
+
<para>
The hardware architecture is the <emphasis>minimum</emphasis>
type of machine required for that specific package. Packages
More information about the Fedora-docs-commits
mailing list