yum-software-management Makefile, 1.1.1.1, 1.2 yum-software-management-en.xml, 1.3, 1.4
Stuart Ellis (elliss)
fedora-docs-commits at redhat.com
Tue Jun 14 22:45:41 UTC 2005
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16841
Modified Files:
Makefile yum-software-management-en.xml
Log Message:
- Updated to use docs-common/
- Split Search section into two for clarity
- Moved admonition on valid package id/names to Searching by Package Name section
- Minor edits and fixes
Index: Makefile
===================================================================
RCS file: /cvs/docs/yum-software-management/Makefile,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- Makefile 1 Jun 2005 21:31:25 -0000 1.1.1.1
+++ Makefile 14 Jun 2005 22:45:38 -0000 1.2
@@ -7,8 +7,8 @@
# Copyright 2003 Tammy Fox, Red Hat, Inc.
###############################################################################
-XSLPDF = ../xsl/main-pdf.xsl
-XSLHTML = ../xsl/main-html.xsl
+XSLPDF = ../docs-common/xsl/main-pdf.xsl
+XSLHTML = ../docs-common/xsl/main-html.xsl
LANG = en
DOCNAME = yum-software-management-$(LANG)
XMLFILE = $(DOCNAME).xml
@@ -17,8 +17,8 @@
html:
@xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
@mkdir -p $(DOCNAME)/stylesheet-images
- @cp ../stylesheet-images/*.png $(DOCNAME)/stylesheet-images
- @cp ../css/fedora.css $(DOCNAME)
+ @cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
+ @cp ../docs-common/css/fedora.css $(DOCNAME)
pdf:
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- yum-software-management-en.xml 12 Jun 2005 21:18:18 -0000 1.3
+++ yum-software-management-en.xml 14 Jun 2005 22:45:38 -0000 1.4
@@ -1,17 +1,17 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../common/fedora-entities-en.ent">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "yum-software-management-0.4.3 (2005-06-12)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "yum-software-management-0.4.4 (2005-06-14)"> <!-- change version of manual and date here -->
-<!ENTITY LEGALNOTICE SYSTEM "../common/legalnotice-en.xml">
+<!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
<!-- Bugzilla bug number for the draft notice -->
<!ENTITY BUG-NUM "155190">
<!ENTITY FCLOCALVER "3">
-<!ENTITY DRAFTNOTICE SYSTEM "../common/draftnotice-en.xml">
+<!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">
]>
@@ -250,40 +250,46 @@
</indexterm>
<para>
Each package file has a long name that indicates several key pieces of
- information. The <command>yum</command> utility may use just the name
- of the package itself, but you may also use other attributes in the file
- name to make queries more specific.
- </para>
- <para>
- For example, this is the full name of a package supplied with &FC;:
+ information. For example, this is the full name of a package supplied with &FC;:
</para>
<screen>
<filename>tsclient-0.132-4.i386.rpm</filename>
</screen>
<para>
- You should use the short name <filename>tsclient</filename> in most
- cases. To specify the exact version of the application, use
- <filename>tsclient-0.132</filename>. Add the hardware architecture to
- the short name and use <filename>tsclient.i386</filename> to specify
- packages for your type of computer. The package listings provided by
- <command>yum</command> itself use the format
- <filename>name.architecture</filename>.
+ 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.
</para>
- <tip>
- <title>Specifying Packages</title>
- <para>
- You may use any of the following formats for
- specifying a package in a <command>yum</command> query: <filename>name</filename>,
- <filename>name.architecture</filename>, <filename>name-version</filename>, <filename>name-version-release</filename>,
- <filename>name-version-release.architecture</filename>, and <filename>epoch:name-version-release.architecture</filename>.
- </para>
- </tip>
+ <para>
+ These are valid for the file shown above:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Package name: <filename>tsclient</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Package name with version number: <filename>tsclient-0.132</filename>
+ </para>
+ </listitem>
+ <listitem>
<para>
- The hardware architecture included in each package name is the
- minimum type of machine required for that specific package. Packages
- with <option>i386</option> run on any current Intel-compatible computer. Packages
- for PowerPC machines, such as Apple Macs, are indicated with <option>ppc</option>.
- Packages with <option>noarch</option> have no architecture requirement.
+ Package name with hardware architecture: <filename>tsclient.i386</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ The hardware architecture is the <emphasis>minimum</emphasis> type of
+ machine required for that specific package. Packages with
+ <option>i386</option> run on any current Intel-compatible computer.
+ Packages for PowerPC machines, such as Apple Macs, are indicated with
+ <option>ppc</option>. Packages with <option>noarch</option> have no
+ architecture requirement.
</para>
<para>
Some software can be optimized for particular types of Intel-compatible
@@ -292,9 +298,15 @@
and <option>x86_64</option>. A
computer with at least an Intel Pentium, VIA C3 or compatible chip is
an <option>i586</option>. Computers with an Intel Pentium II and above, or a current
- model of AMD chip, are <option>i686</option> machines. 64-bit PCs can
- use <option>x86_64</option> packages for full 64-bit support.
+ model of AMD chip, are <option>i686</option> machines. 64-bit PCs use <option>x86_64</option> packages for full 64-bit support.
</para>
+ <note>
+ <title>Other Naming Conventions are Supported</title>
+ <para>
+ Refer to <xref linkend="sn-searching-packages-byname"></xref> for
+ more information on specifying packages by name or type.
+ </para>
+ </note>
</section>
</section>
@@ -475,7 +487,7 @@
<section id="sn-searching-packages">
- <title>Searching for Software Packages with <command>yum</command></title>
+ <title>Searching for Software with <command>yum</command></title>
<indexterm>
<primary>packages, locating</primary>
</indexterm>
@@ -496,11 +508,14 @@
<filename>PalmPilot</filename> packages.
</para>
</note>
-<para>
+
+ <section id="sn-searching-packages-byname">
+ <title>Searching by Package Name and Attributes</title>
+ <para>
To search for a specific package by name, use the <option>list</option>
function. For example, to search for the package
<filename>tsclient</filename> the command would be:
- </para>
+ </para>
<screen>
<userinput>yum list <replaceable>tsclient</replaceable></userinput>
</screen>
@@ -511,13 +526,22 @@
<screen>
<userinput>yum list <replaceable>tsclient-0.132</replaceable></userinput>
</screen>
- <note>
+ <tip>
<title>Package Attributes</title>
<para>
- See <xref linkend="sn-package-names"></xref> for information on
- package attributes.
+ You may use any of the following formats for
+ specifying a package in a <command>yum</command> query: <filename>name</filename>,
+ <filename>name.architecture</filename>, <filename>name-version</filename>, <filename>name-version-release</filename>,
+ <filename>name-version-release.architecture</filename>, and
+ <filename>epoch:name-version-release.architecture</filename>.
</para>
- </note>
+ </tip>
+ </section>
+
+
+ <section id="sn-searching-packages-advanced">
+ <title>Advanced Searches</title>
+
<para>
If you do not know the name of the package, use either the
<option>search</option> or <option>provides</option> options.
@@ -559,6 +583,7 @@
</para>
</tip>
+ </section>
<section id="sn-package-matches">
<title>Understanding Matches</title>
More information about the Fedora-docs-commits
mailing list