yum-software-management yum-software-management-en.xml,1.11,1.12
Stuart Ellis (elliss)
fedora-docs-commits at redhat.com
Mon Jul 18 19:25:38 UTC 2005
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15747
Modified Files:
yum-software-management-en.xml
Log Message:
Style fixes.
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- yum-software-management-en.xml 18 Jul 2005 00:07:57 -0000 1.11
+++ yum-software-management-en.xml 18 Jul 2005 19:25:35 -0000 1.12
@@ -158,33 +158,33 @@
<term>
The Website for <command>yum</command> is:
</term>
- <listitem>
- <para>
- <ulink url="http://linux.duke.edu/projects/yum/">http://linux.duke.edu/projects/yum/</ulink>
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <ulink url="http://linux.duke.edu/projects/yum/">http://linux.duke.edu/projects/yum/</ulink>
+ </para>
+ </listitem>
</varlistentry>
<varlistentry>
- <term>
+ <term>
The mailing list for <command>yum</command> users is:
</term>
-<listitem>
- <para>
- <ulink url="https://lists.dulug.duke.edu/mailman/listinfo/yum/">https://lists.dulug.duke.edu/mailman/listinfo/yum/</ulink>
- </para>
-</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://lists.dulug.duke.edu/mailman/listinfo/yum/">https://lists.dulug.duke.edu/mailman/listinfo/yum/</ulink>
+ </para>
+ </listitem>
</varlistentry>
<varlistentry>
-<term>
+ <term>
The archive for the <command>yum</command> development mailing list is:
</term>
- <listitem>
- <para>
- <ulink url="https://lists.dulug.duke.edu/pipermail/yum-devel/">https://lists.dulug.duke.edu/pipermail/yum-devel/</ulink>
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://lists.dulug.duke.edu/pipermail/yum-devel/">https://lists.dulug.duke.edu/pipermail/yum-devel/</ulink>
+ </para>
+ </listitem>
</varlistentry>
</variablelist>
</section>
@@ -265,7 +265,9 @@
<para>
You may also manage related packages as sets by using the
<firstterm>package groups</firstterm> provided by the &FED;
- repositories. Third-party repositories may add packages to these groups, or provide packages in additional groups where necessary.
+ repositories. Third-party repositories may add packages to these
+ groups, or provide packages in additional groups where
+ necessary.
</para>
<!-- SE: Some repositories use groups and some don't: I've tried to put this nicely. -->
<para>
@@ -331,11 +333,12 @@
<para>
Use just the name of the package itself with
<command>yum</command>, except when it is necessary to specify
- the exact version or type. To specify the exact version of the
- application, use <filename>name-version</filename>. The package
- listings provided by <command>yum</command> itself use the
- format <filename>name.architecture</filename>, to specify the
- type of computer that the package is intended for.
+ the exact version or type. For example, use
+ <filename>name-version</filename> to specify the exact version
+ of the application. The package listings provided by
+ <command>yum</command> itself use the format
+ <filename>name.architecture</filename>, to specify the type of
+ computer that the package is intended for.
</para>
<para>
@@ -642,7 +645,7 @@
<title>New Software Versions Require Reloading</title>
<para>
- If a piece of software is use whilst it is updated then the
+ If a piece of software is in use whilst it is updated then the
old version remains active until the software is next loaded.
Services are reloaded by restarting the service. Kernel
updates take effect the next time that the system is booted.
@@ -725,10 +728,10 @@
<primary>searching for packages</primary>
</indexterm>
<para>
- You may use <command>yum</command> to find software that is
- available from the defined repositories, or is already installed
- on your system. Searches automatically include both installed and
- available packages.
+ Use the search features of <command>yum</command> to find software
+ that is available from the defined repositories, or is already
+ installed on your system. Searches automatically include both
+ installed and available packages.
</para>
<note>
@@ -775,6 +778,9 @@
<para>
If you do not know the name of the package, use either the
<option>search</option> or <option>provides</option> options.
+ </para>
+
+ <para>
<option>Search</option> checks the names, descriptions,
summaries and listed package maintainers of all of the available
packages to find those that match. For example, to search for
@@ -1160,14 +1166,14 @@
</para>
<para>
- You should always check the Website of the provider for
- compatibility information before attempting to use a repository.
- Repositories often provide packages that are specifically
- intended for use with packages that are supplied by other
- repositories. In some cases separate third-party repository
- providers may each offer different versions of the same
- software, preventing those repositories from being safely used
- together by your &FC; system.
+ Before attempting to use a repository, read the Website for
+ information on package compatibility. . Repositories often
+ provide packages that are specifically intended for use with
+ packages that are supplied by other repositories. In some cases
+ separate third-party repository providers may each offer
+ different versions of the same software, preventing those
+ repositories from being safely used together by your &FC;
+ system.
</para>
<para>
@@ -1291,12 +1297,15 @@
<primary>public keys, removing</primary>
</indexterm>
<para>
- If you will not be using any more packages from that source then
- you should also remove their public key from the
- <command>rpm</command> keyring. To remove a public key you first
- need to know the identification name used by
- <command>rpm</command>. You may view the details of all public
- keys with the command:
+ In addition, remove the public key for the package provider from
+ the <command>rpm</command> keyring, if you will not be using any
+ more packages from that source.
+ </para>
+
+ <para>
+ To remove a public key from the keyring you must know the
+ identification name used by <command>rpm</command>. Run this
+ command to view the details of the public keys on the keyring:
</para>
<screen>
<userinput>rpm -qi gpg-pubkey-*</userinput>
@@ -1397,9 +1406,7 @@
from &FC; in order to be able to make repositories.
</para>
</note>
-
<!-- SE: The instructions below won't work as is and need amending, since the example directory can only be accessed with root privileges by default. -->
-
<para>
To make a directory into a <command>yum</command> repository,
carry the following tasks. These instructions assume that the
@@ -1433,7 +1440,8 @@
<listitem>
<para>
In the terminal window type: <userinput>createrepo -g
- <replaceable>/var/www/repository/groups.xml</replaceable> <replaceable>/var/www/repository/</replaceable></userinput>.
+ <replaceable>/var/www/repository/groups.xml</replaceable>
+ <replaceable>/var/www/repository/</replaceable></userinput>.
</para>
</listitem>
<listitem>
@@ -1459,10 +1467,10 @@
Create a definition file for this new repository. If you are
distributing packages that you have created yourself then you
also need to make the GPG public key for your signature
- available, so that others can verify the packages. The simplest
- way to make these files available is to put the public key and
- repository definition files on the same Website or FTP site as
- the repository.
+ available, so that others are able to verify the packages. The
+ simplest way to make these files available is to put the public
+ key and repository definition files on the same Website or FTP
+ site as the repository.
</para>
<para>
@@ -1641,7 +1649,7 @@
<para>
If possible, list more than one directory or server that holds a
copy of the repository. This enables <command>yum</command> to
- use another repository if the first is unavailable. By default
+ use another repository if the first is unavailable. By default,
<command>yum</command> randomly selects repositories from the
<command>baseurl</command> list. To force <command>yum</command>
to use them in sequence, add the option
@@ -1649,13 +1657,13 @@
</para>
<para>
- It is also good practice to use variables like
- <command>$releasever</command> in the URL, rather than setting
- these to a specific value. The available variables are listed on
- the <command>man</command> page for
- <filename>yum.conf</filename>. Using variables enables the same
+ Write the URL with variables, such as
+ <command>$releasever</command>, rather than specifying fixed
+ values for these attributes. Using variables enables the same
definition to function when your system is upgraded to a later
version, or if the configuration is copied to another machine.
+ The available variables are listed on the <command>man</command>
+ page for <filename>yum.conf</filename>.
</para>
<para>
@@ -1672,8 +1680,8 @@
<command>yum</command> will access the FTP server with the
username <command>yum-user</command> and the password
<command>qwerty</command>. The <command>failovermethod</command>
- ensures that <command>yum</command> will check the copy on the
- local machine, before trying the servers in sequence.
+ ensures that <command>yum</command> checks the copy on the local
+ system, before trying the servers in sequence.
</para>
<example id="yum-repo-multidir-example">
@@ -1712,12 +1720,12 @@
</indexterm>
<para>
Whenever a package is added, or replaced with a different
- version, you must run <command>createrepo</command> again for
- the index files to be updated. If you are mirroring an existing
- repository then you may assume that the site administrator
- updates the indexes, but for safety you should add this to your
- synchronization scripts. The <command>createrepo</command>
- utility can be run as frequently as you wish.
+ version, you must run <command>createrepo</command> again to
+ update the index files. If you are mirroring an existing
+ repository then add <command>createrepo</command> to your
+ synchronization scripts, even though the original copy may have
+ index files. This ensures that the indexes on your copy of the
+ site are accurate.
</para>
</section>
</section>
More information about the Fedora-docs-commits
mailing list