stateless-linux Makefile,1.2,1.3
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/stateless-linux
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28853
Modified Files:
Makefile
Log Message:
Fix stateless-linux howto Makefile to new standards
Index: Makefile
===================================================================
RCS file: /cvs/docs/stateless-linux/Makefile,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Makefile 28 Jun 2005 22:33:46 -0000 1.2
+++ Makefile 15 Nov 2005 23:20:24 -0000 1.3
@@ -1,31 +1,26 @@
###############################################################################
# Makefile for RHLP docs project
# Created by: Tammy Fox <tfox(a)redhat.com>
-# Last edited by: Tammy Fox <tfox(a)redhat.com>
+# Last edited by: Tommy Reynolds <Tommy.Reynolds(a)MegaCoder.com>
# WARNING: need passivetex 1.24 for pdf generation to work
# License: GPL
# Copyright 2003 Tammy Fox, Red Hat, Inc.
+# Copyright 2005 Tommy Reynolds, MegaCoder.com
###############################################################################
-XSLPDF = ../docs-common/xsl/main-pdf.xsl
-XSLHTML = ../docs-common/xsl/main-html.xsl
-LANG = en
-DOCNAME = stateless-linux-HOWTO-$(LANG)
-XMLFILE = $(DOCNAME).xml
+LANGUAGES = en
+DOCBASE = stateless-linux-HOWTO
+XMLEXTRAFILES-en =
######################################################
include ../docs-common/Makefile.common
######################################################
-html:
- @xmlto html -x $(XSLHTML) -o $(DOCNAME) $(XMLFILE)
- @mkdir -p $(DOCNAME)/stylesheet-images
- @cp ../docs-common/stylesheet-images/*.png $(DOCNAME)/stylesheet-images
- @cp ../docs-common/css/fedora.css $(DOCNAME)
-
-pdf:
- @xmlto pdf -x $(XSLPDF) $(XMLFILE)
-######################################################
-
-clean:
- @rm -rfv *.html *.pdf *.tex $(DOCNAME) $(DOCNAME).tar.gz
+# If you want to add additional steps to any of the
+# targets defined in "Makefile.common", be sure to use
+# a double-colon in your rule here. For example, to
+# print the message "FINISHED AT LAST" after building
+# the HTML document version, uncomment the following
+# line:
+#${DOCNAME}/index.html::
+# echo FINISHED AT LAST
18 years, 5 months
docs-common Makefile.common,1.12,1.13
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28596
Modified Files:
Makefile.common
Log Message:
Added one new target, "showvars". The new target is used to grab variables from inside the document-specific makefiles for use in external bash scripts. Additional variables can be added to the list.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- Makefile.common 30 Oct 2005 19:15:40 -0000 1.12
+++ Makefile.common 15 Nov 2005 23:10:46 -0000 1.13
@@ -51,7 +51,7 @@
# PUT NO TARGETS BEFORE THIS ONE, not even in your base Makefile
# In a properly-constructed Makefile, this will be the default target
-TARGETS=all tarball pdf html html-nochunks clean distclean
+TARGETS=all tarball pdf html html-nochunks clean distclean showvars
.PHONY: ${TARGETS}
all:: html html-nochunks tarball # pdf
@@ -141,6 +141,10 @@
distclean clean:: $(foreach LANG,${LANGUAGES},${DOCBASE}-${LANG}-clean)
$(foreach LANG,${LANGUAGES},$(eval $(call CLEAN_template,${LANG})))
+
+showvars::
+ @echo "DOCBASE=\"$(DOCBASE)\""
+ @echo "LANGUAGES=\"$(LANGUAGES)\""
#
#########################################################################
# End of Makefile.common
18 years, 5 months
docs-common/bin active,NONE,1.1
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26924/bin
Added Files:
active
Log Message:
This file will track folders for docs that should be built in any bulk action for DocsRawhide.
--- NEW FILE active ---
documentation-guide
stateless-linux
selinux-faq
install-guide
release-notes
developer-guide
mirror-tutorial
jargon-buster
rpm-guide
yum-software-management
translation-guide-windows
selinux-apache
translation-guide
18 years, 5 months
yum-software-management yum-software-management-zh_CN.xml, NONE, 1.1 Makefile, 1.5, 1.6
by fedora-docs-commits@redhat.com
Author: bbbush
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10226
Modified Files:
Makefile
Added Files:
yum-software-management-zh_CN.xml
Log Message:
--- NEW FILE yum-software-management-zh_CN.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!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 "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
<!ENTITY BOOKID "yum-software-management-1.0.4 (2005-11-15)">
<!-- change version of manual and date here --><!-- Bugzilla bug number for the draft notice --><!ENTITY BUG-NUM "155190">
<!ENTITY FCLOCALVER "4">
]>
<article id="yum-software-management" lang="zh_CN">
<articleinfo><title>������ <command>yum</command> ������������</title><copyright><year>2005</year><holder>Stuart Ellis</holder></copyright><copyright><year>2005</year><holder>bbbush (bbbush.yuan(a)gmail.com)</holder></copyright><authorgroup><author><surname>Ellis</surname><firstname>Stuart</firstname></author></authorgroup> &LEGALNOTICE; <revhistory><revision><revnumber>0.4</revnumber><date>2005-06-01</date><authorinitials>StuartEllis</authorinitials><revdescription><para>������ CVS���</para></revdescription></revision><revision><revnumber>0.5</revnumber><date>2005-07-19</date><authorinitials>StuartEllis</authorinitials><revdescription><para>��� &FC; &FCLOCALVER; ���������</para></revdescription></revision><revision><revnumber>0.6</revnumber><date>2005-07-25</date><authorinitials>PaulWFrields</authorinitials><revdescription><para>������������������������������ BETA���</para></revdescription></revision><revision><revnumber>1.0</revnumber><date>2005-08-13</date><authorinitials!
>PaulWFrields</authorinitials><revdescription><para>������������������������������</para></revdescription></revision><revision><revnumber>1.0.1</revnumber><date>2005-08-18</date><authorinitials>StuartEllis</authorinitials><revdescription><para>������������������������������������������������������������������</para></revdescription></revision><revision><revnumber>1.0.2</revnumber><date>2005-08-26</date><authorinitials>StuartEllis</authorinitials><revdescription><para>������������������������������</para></revdescription></revision><revision><revnumber>1.0.3</revnumber><date>2005-10-13</date><authorinitials>PaulWFrields</authorinitials><revdescription><para>������������ (#170584)���</para></revdescription></revision><revision><revnumber>1.0.4</revnumber><date>2005-11-15</date><authorinitials>StuartEllis</authorinitials><revdescription><para>��������������������������������������� #166122���</para></revdescription></revision></revhistory></articleinfo>
<section id="sn-introduction">
<title>������</title>
<section id="sn-purpose">
<title>������</title>
<para>��������������������� &FED; ������������������������������������������������������ &FED; ��������������������������������� <command>yum</command> ������������������</para>
</section>
<section id="sn-software-management-audience">
<title>������</title>
<para>������������������������������������ &FED; ���������</para>
</section>
<section id="sn-software-management-usingdoc">
<title>������������������</title>
<para>������������������ <command>yum</command> ��������������������������������������������������������������������������������������������������������������������������������������������������� <command>yum</command> ��������������� <xref linkend="sn-software-management-concepts"/>��������������� Linux ��������������� <xref linkend="sn-managing-packages"/> ���������</para>
<note>
<title>��������������� &FED;</title>
<para>������������������ <command>yum</command> ������������������ &FED; &FCLOCALVER; ������������ &FED; 3 ��������������������� <xref linkend="sn-authorizing-package-sources"/> ������������������������ <command>yum</command>���</para>
</note>
<para>��������������������������������������������� <filename>tsclient</filename>��������������� &FC; ���������<filename>tsclient</filename> ������������������������������������������������������������������������������������������������������������������ <menuchoice><guimenu>Applications</guimenu><guisubmenu>Internet</guisubmenu><guimenuitem>Terminal Server Client</guimenuitem></menuchoice> ������������������������������������������������ <filename>tsclient</filename> ������������������������������������&FED; ��������������������������������� <filename>MySQL Database</filename> ������</para>
<important>
<title>��������� root ������������</title>
<para>��������������� <systemitem class="username">root</systemitem> ��������������������������������� &FED; ��������������������������������������������������� <systemitem class="username">root</systemitem> ��������������������������� <systemitem class="username">root</systemitem> ������������������������ <command>su <option>-c</option></command> ������������������������������</para>
</important>
</section>
<section id="sn-yum-additional-resources">
<title>������������</title>
<indexterm>
<primary>yum</primary>
<secondary>������</secondary>
</indexterm> <indexterm>
<primary>yum</primary>
<secondary>���������</secondary>
</indexterm>
<para>��������������������� <command>yum</command> ��������������������������������������� <command>man</command> ������������ <command>yum(8)</command> ��� <filename>yum.conf(5)</filename> ���������������������������������</para>
<screen>
<userinput>man yum
man yum.conf</userinput>
</screen>
<indexterm>
<primary>yum</primary>
<secondary>������</secondary>
</indexterm> <indexterm>
<primary>yum</primary>
<secondary>������������</secondary>
</indexterm>
<para>��������������������������� <command>yum</command> ���������������</para>
<variablelist>
<varlistentry>
<term>������������</term>
<listitem>
<para>
<ulink url="http://linux.duke.edu/projects/yum/"/>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>���������������������</term>
<listitem>
<para>
<ulink url="https://lists.dulug.duke.edu/mailman/listinfo/yum/"/>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>���������������������</term>
<listitem>
<para>
<ulink url="https://lists.dulug.duke.edu/pipermail/yum-devel/"/>
</para>
</listitem>
</varlistentry>
</variablelist>
<tip>
<title>������������ &BZ;</title>
<para>������������������������������������������������������ &BZ-URL; ������������������������������������������������������������������������������������������������������������ <command>yum</command> ��������������������� &BZ; ��������������������� &FED; ���������������������������</para>
</tip>
</section>
</section>
<section id="sn-software-management-concepts">
<title>������������������</title>
<section id="sn-about-packages">
<title>���������������</title>
<indexterm>
<primary>���������</primary>
<secondary>������</secondary>
</indexterm>
<para>&FED; ��������������������������������� RPM <firstterm>���������</firstterm> ���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������&FED; ��������������������� &FC; ���������������������������������������������������������������</para>
<para>������������������������������������������������������������������������������������������ GPG <firstterm>������</firstterm> ������������������������<command>yum</command> ��� <command>rpm</command> ��������������������� <firstterm>keyring</firstterm>���������������������������������������������������������������������������������������������������������������������������������</para>
<note>
<title>&FED; ������������������������������������</title>
<para>&FP; ��������������������������������������������������������� &FED; ������������������������������������������������</para>
</note>
</section>
<section id="sn-about-repositories">
<title>������������</title>
<indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm>
<para><firstterm>������</firstterm> ������������������������������������������������������������������������������������������������������������������ <command>yum</command>������������������������������������������������������ RPM ���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������</para>
<para>��������������������������������������������� &FED; ������������������������������&FC; ������������������������������������������������������������������������</para>
<variablelist>
<varlistentry>
<term>Base</term>
<listitem>
<para>������ &FC; ���������������������������������������</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Updates</term>
<listitem>
<para>Base ���������������������������������</para>
</listitem>
</varlistentry>
<varlistentry>
<term>&EX;</term>
<listitem>
<para>���������������������������</para>
</listitem>
</varlistentry>
</variablelist>
<note>
<title>��������������� &FED;</title>
<para>&FED; &FCLOCALVER; ������������������������������������������ &FED; 3 ������������������������������������������ &FEX;��������������� <xref linkend="sn-using-repositories"/> ���������</para>
</note>
<warning>
<title>&FED; ������������</title>
<para>&FC; ��������������������������������������������������������������������������������������������������������������������������������������������������������� &FED; ������������������������������������<filename>fedora-devel</filename> (Rawhide), <filename>fedora-extras-devel</filename>, ��� <filename>updates-testing</filename>���</para>
</warning>
<para>������������������������������������������������������������������������ &FED; ��������������������������������������� &FED; ��������������������������������������������� <xref linkend="sn-using-repositories"/>���</para>
<indexterm>
<primary>���������</primary>
<secondary>������</secondary>
</indexterm>
<para>������������ &FED; ��������������� <firstterm>���������</firstterm> ���������������������������������������������������������������������������������������������������������������������������������������������</para>
<!-- SE: Some repositories use groups and some don't: I've tried to put this nicely. -->
<!-- SE: Using the admonition for this is not optimal, it just doesn't fit anywhere else. -->
<note>
<title>������������������</title>
<para>��������������� &FED; ������������������������������������������������ <command>su -c 'yum grouplist'</command>���</para>
</note>
<para>���������������������������������������������������������������������������������������������������������������������������������������������������������������</para>
<caution>
<title>���������������������������������</title>
<para>��������������������������������������������������������������������������������������������������������������������������������������������������������������������������� &FED; ������������������������</para>
<para>��������������� <command>yum</command> ��������������������������������������������������������� <command>yum</command> ������������������������������������������������������ <xref linkend="sn-yum-installing-frompackage"/>���</para>
</caution>
</section>
<section id="sn-about-dependencies">
<title>������������������</title>
<indexterm>
<primary>������������</primary>
<secondary>������</secondary>
</indexterm>
<para>&FED; ��������������������������������������� <firstterm>���</firstterm>������������������������������������������������������������������������������������������������������������������������ <firstterm>������</firstterm>���������������������������������������&FED; ��������������������������������������������� RPM ��������������������������������������� RPM ������������</para>
<para><command>yum</command> ������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������<command>yum</command> ������������������������������������������</para>
</section>
<section id="sn-package-names">
<title>���������������������</title>
<indexterm>
<primary>���������</primary>
<secondary>���������������</secondary>
</indexterm> <indexterm>
<primary>���������</primary>
<secondary>������</secondary>
</indexterm>
<para>��������������������������������������������������������������������������������������������������������� &FC; ��� <filename>tsclient</filename> ���������������������</para>
<screen>
<filename>tsclient-0.132-6.i386.rpm</filename>
</screen>
<para>������������������������������������������������������������������������</para>
<itemizedlist>
<listitem>
<para>������������������<filename>tsclient</filename></para>
</listitem>
<listitem>
<para>���������������������������������������������������<filename>tsclient-0.132-6</filename></para>
<!-- In what instances is the release number not needed? For many -->
<!-- package updates, only the release number might change. Although it -->
<!-- might be superfluous, it's never *bad* to include it, right? [PWF] -->
</listitem>
<listitem>
<para>���������������������������������������<filename>tsclient.i386</filename></para>
</listitem>
</itemizedlist>
<para>���������������������<command>yum</command> ��� <filename>������.������</filename> ��������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� <emphasis>������</emphasis> ���������</para>
<variablelist>
<varlistentry>
<term>i386</term>
<listitem>
<para>��������������������� Intel ���������������</para>
</listitem>
</varlistentry>
<varlistentry>
<term>noarch</term>
<listitem>
<para>������������������</para>
</listitem>
</varlistentry>
<varlistentry>
<term>ppc</term>
<listitem>
<para>������ PowerPC ��������������� Apple Power Macintosh</para>
</listitem>
</varlistentry>
<varlistentry>
<term>x86_64</term>
<listitem>
<para>������ 64 ��� Intel ������������������ Opterons</para>
</listitem>
</varlistentry>
</variablelist>
<para>��������������������������������� Intel ��������������������� <option>i386</option>, <option>i586</option>, <option>i686</option> ��� <option>x86_64</option> ������������������������������������������������������ Intel ���������VIA C3 ������������������������������������������������ <option>i586</option> ������������������������������ Intel ��������������������������������������������������������� AMD ������������������������������ <option>i686</option> ������������</para>
<para>��� <command>yum</command> ������������������������������������������������������<command>yum</command> ������������������������������������������������������������������������������������</para>
<para>������������������������������������������������������������������������ <command>yum</command> ���������������������������������������������������������������������������������������������������������������������������</para>
<tip>
<title>���������������</title>
<para>������������ <command>yum</command> ���������������������������������������������������������<replaceable>name</replaceable>, <replaceable>name.architecture</replaceable>, <replaceable>name-version</replaceable>, <replaceable>name-version-release</replaceable>, <replaceable>name-version-release.architecture</replaceable>, ��� <replaceable>epoch:name-version-release.architecture</replaceable>���</para>
</tip>
</section>
</section>
<section id="sn-software-management-tools">
<title>&FC; ������������������������</title>
<indexterm>
<primary>������/������������������������</primary>
</indexterm> <indexterm>
<primary>������������</primary>
</indexterm> <indexterm>
<primary>up2date</primary>
</indexterm>
<para><command>yum</command> ���������������������������������������������&FC; ������������������������������������������ <command>yum</command> ������������</para>
<para>������������������������ <application>Alert Icon</application>������������������������������������������������������������������������������������������������������������������������������������������������������������������ <application>up2date</application> ������������������������������������������������������</para>
<para>&FC; ������������������ <application>system-config-packages</application> ������������������������������������������������������������������������ <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guimenuitem>Add/Remove Applications</guimenuitem></menuchoice>������ <application>up2date</application> ��� <command>yum</command> ���������<application>system-config-packages</application> ������������ &FC; ������������������������������������������������������������������������������������������������������������������</para>
<para>��������������� <command>rpm</command> ������������������������������������������ RPM ������������������������������������������������������������������������������������������ <command>rpm</command> ������������������������������������������������������������������������������������������������<command>yum</command> ���������������������������������</para>
<caution>
<title>���������������������</title>
<para><application>up2date</application> ��� <command>yum</command> ���������������������������������������������������������������������������������������������������������</para>
</caution>
</section>
<section id="sn-managing-packages">
<title>������ <command>yum</command> ������������</title>
<indexterm>
<primary>yum</primary>
<secondary>������������</secondary>
</indexterm>
<para>������ <command>yum</command> ���������������������������������������������������������</para>
<para>
<itemizedlist>
<listitem>
<para>������������������������</para>
</listitem>
<listitem>
<para>������������������������������������������</para>
</listitem>
<listitem>
<para>������������������������������������</para>
</listitem>
<listitem>
<para>������������������������������������������</para>
</listitem>
</itemizedlist>
</para>
<!-- SE: This duplicates text from the admonition in sn-about-repositories. It's here as well because the Fedora site has a link straight to this section -->
<important>
<title>������������������������������������</title>
<para>��������������� <command>yum</command> ��������������������������������������������������������� <command>yum</command> ������������������������������������������������������ <xref linkend="sn-yum-installing-frompackage"/>���</para>
</important>
<para>������ <command>yum</command> ������������������������������������������������������������/������������</para>
<para>���������������������<command>yum</command> ���������������������������������������������������������������������������������������������������<command>yum</command> ���������������������������������������������������������������������</para>
<para>���������������������������<command>yum</command> ���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������</para>
<example id="yum-transaction-format">
<title><command>yum</command> ���������������������</title>
<para>��������������������� <filename>tsclient</filename> ���������������</para>
<screen>
<computeroutput>=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
tsclient i386 0.132-6 base 247 k
Installing for dependencies:
rdesktop i386 1.4.0-2 base 107 k
Transaction Summary
=============================================================================
Install 2 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 355 k
Is this ok [y/N]:</computeroutput>
</screen>
</example>
<para>��������������������������������������� <keycap>y</keycap> ��������������������������������� <keycap>N</keycap> ��� <keycap>Enter</keycap>(������)���<command>yum</command> ������������������������������������</para>
<note>
<title>���������������</title>
<para><command>yum</command> ������������������������������������������������������������������������������������</para>
</note>
<para><command>yum</command> ��������������������������������������������������������� <command>rpm</command> ���������������������</para>
<example id="yum-publickey-import">
<title><command>yum</command> ���������������������</title>
<para>������������������������������������</para>
<screen>
<computeroutput>warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
public key not available for tsclient-0.132-6.i386.rpm
Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora(a)redhat.com>"
Is this ok [y/N]:</computeroutput>
</screen>
</example>
<para>��������������������������������� <keycap>y</keycap> ��������������������������������������������������� <keycap>N</keycap> ��� <keycap>Enter</keycap>(������)���<command>yum</command> ������������������������������������</para>
<para>���������������������������������������������<command>yum</command> ������������������������������������������������������������������������������������������������������������������������������<command>yum</command> ������������������������������������</para>
<para>��������������������������������������� <filename>/var/log/yum.log</filename> ��������������������������������������������� <systemitem class="username">root</systemitem> ������������������</para>
<tip>
<title>���������������</title>
<para><command>yum</command> ��������������������������������������������������������������������������������������� <filename>/var/cache/yum/</filename> ������������������������������������������������������������������������������������������������������������������������������������������������������������������������������</para>
</tip>
<section id="sn-yum-installing-withrepositories">
<title>������ <command>yum</command> ���������������</title>
<indexterm>
<primary>������������</primary>
<see>���������������</see>
</indexterm> <indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm>
<para>��������������� <filename>tsclient</filename>������������������</para>
<screen>
<userinput>su -c 'yum install <replaceable>tsclient</replaceable>'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<para>������������������ <filename>MySQL Database</filename>������������������</para>
<screen>
<userinput>su -c 'yum groupinstall "<replaceable>MySQL Database</replaceable>"'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<important>
<title>������������������������</title>
<para>������������������������������������&FED; ������������������������������������������������������������������������������������������������ <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guisubmenu>Server Settings</guisubmenu><guimenuitem>Services</guimenuitem></menuchoice>������������������������������ <command>chkconfig</command> ��� <command>service</command>���</para>
</important>
</section>
<section id="sn-yum-updating-withrepositories">
<title>������ <command>yum</command> ������������</title>
<indexterm>
<primary>������</primary>
<secondary>���������</secondary>
</indexterm> <indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm>
<para>��������� <filename>tsclient</filename> ���������������������������������</para>
<screen>
<userinput>su -c 'yum update <replaceable>tsclient</replaceable>'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<important>
<title>���������������������������������</title>
<para>������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������</para>
</important>
<para>������������������ <filename>MySQL Database</filename> ������������������������������������</para>
<screen>
<userinput>su -c 'yum groupupdate "<replaceable>MySQL Database</replaceable>"'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<note>
<title>������������������</title>
<para>��������������� &FED; ��������������������������������� <xref linkend="sn-updating-your-system"/> ���������������������</para>
</note>
</section>
<section id="sn-yum-removing-software">
<title>������ <command>yum</command> ������������</title>
<indexterm>
<primary>������������</primary>
</indexterm> <indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm>
<para>������������������<command>yum</command> ������������������������������������������������������������������������������������������������������������������������������������������������������������������</para>
<para>��������� <filename>tsclient</filename> ������������������������</para>
<screen>
<userinput>su -c 'yum remove <replaceable>tsclient</replaceable>'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<para>������������������ <filename>MySQL Database</filename> ������������������������������������</para>
<screen>
<userinput>su -c 'yum groupremove "<replaceable>MySQL Database</replaceable>"'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<note>
<title>������������������������������������</title>
<para>������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������</para>
</note>
</section>
</section>
<section id="sn-searching-packages">
<title>������ <command>yum</command> ������������</title>
<indexterm>
<primary>���������</primary>
<secondary>������</secondary>
</indexterm> <indexterm>
<primary>������</primary>
<secondary>���������</secondary>
</indexterm>
<para>������ <command>yum</command> ������������������������������������������������������������������������������������������������������������������������������������</para>
<para>���������������������������������������������������������������������������������������������������������������</para>
<section id="sn-searching-packages-byname">
<title>������������������������������</title>
<para>������������������������������ <option>list</option> ������������������������ <filename>tsclient</filename>������������������</para>
<screen>
<userinput>su -c 'yum list <replaceable>tsclient</replaceable>'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<para>��������������������������������������������������������������������������������������������������� <filename>tsclient</filename> ��� 0.132 ���������������������</para>
<screen>
<userinput>su -c 'yum list <replaceable>tsclient-0.132</replaceable>'</userinput>
</screen>
<note>
<title>���������������������</title>
<para>������ <xref linkend="sn-package-names"/>������������������������������������������������������������������������</para>
</note>
</section>
<section id="sn-searching-packages-advanced">
<title>������������</title>
<para>������������������������������������������ <option>search</option> ��� <option>provides</option> ��������������������������������� <command>yum</command> ���������������������������������������������������������������������������</para>
<para><option>search</option> ������������������������������������������������������������������������������������������������������������������������������������������������������ PalmPilots ���������������������������</para>
<screen>
<userinput>su -c 'yum search <replaceable>PalmPilot</replaceable>'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<para><option>provides</option> ������������������������������������������������������������������������ <option>search</option> ��������������������������� <command>yum</command> ���������������������������������������������</para>
<para>��������������������������� <filename>libneon</filename> ������������������������</para>
<screen>
<userinput>su -c 'yum provides <replaceable>libneon</replaceable>'</userinput>
</screen>
<para>������������������������ MTA (Mail Transport Agent, ������������������) ������������������������������ <filename>mta</filename> ���������������</para>
<screen>
<userinput>su -c 'yum provides <replaceable>MTA</replaceable>'</userinput>
</screen>
<para>��������������������������������������� <systemitem class="username">root</systemitem> ������������������</para>
<para>���������������������������������������������������������������<option>?</option> ���������������������������<option>*</option> ������ 0 ��������������������������������������������������������� (<option>\</option>)���</para>
<para>��� <option>list</option> ��������������� <filename>tsc</filename> ���������������������������</para>
<screen>
<userinput>su -c 'yum list <replaceable>tsc\*</replaceable>'</userinput>
</screen>
<tip>
<title>���������������</title>
<para>������ Perl ��� Python ���������������������������������������������</para>
</tip>
</section>
<section id="sn-package-matches">
<title>������������</title>
<para>������ <command>yum</command> ������������������������������������������������������������������������������������������������������������������������������������������������������������������������</para>
<para>��������������� <filename>shadowutils</filename> ��� <filename>shadow-util</filename> ��������������������� <filename>shadow-utils</filename> ������������������������������ <filename>shadow-util\?</filename> ��� <filename>shadow\*</filename>������������������������������������������������������</para>
</section>
</section>
<section id="sn-updating-your-system">
<title>������ <command>yum</command> ������������������</title>
<indexterm>
<primary>������</primary>
<secondary>������������</secondary>
</indexterm> <indexterm>
<primary>yum</primary>
<secondary>������������������</secondary>
</indexterm>
<para>������ <option>update</option> ��������������������� &FED; ���������������������������������������������������������</para>
<para>������������������������������������������������</para>
<screen>
<userinput>su -c 'yum update'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������</para>
<section id="sn-automatic-updating">
<title>������������������������</title>
<indexterm>
<primary>������������</primary>
</indexterm>
<para>&FC; ������ <filename>yum</filename> ������������������������������������������������������������������������������������������������������������������</para>
<screen>
<userinput>su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<note>
<title>������������������������������</title>
<para>��������������������������� <command>yum</command> ������������������������������������������ <filename>/etc/rc.d/init.d/yum</filename>������������������������������ <filename>/etc/cron.daily/yum.cron</filename>������������������ <command>cron</command> ���������������������������������������������������������������</para>
</note>
</section>
</section>
<section id="sn-using-repositories">
<title>������������������������</title>
<indexterm>
<primary>&FEX;</primary>
</indexterm> <indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm> <indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm>
<para>&FED; ������������������ &FP; ������������������������ &FEX;������������������������ &FC; ������������������</para>
<note>
<title>��������������� &FC; ��� &FEX; ������</title>
<para>��������������������� &FED; 3 ������������ &FEX;��������� <ulink url="http://fedora.redhat.com/projects/extras/"/> ��������������������� &FED; 1 ��� &FED; 2 ������������������������������ <ulink url="http://www.fedora.us/"/>���</para>
</note>
<para>������ &FP; ������������������������������������������������������������������������������������������������������������������������ &FED; ���������������������������<ulink url="http://www.jpackage.org/"/> ������������ Java ���������������������</para>
<section id="sn-adding-repositories">
<title>������������������������������</title>
<indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm>
<para>������������������������������������������������������ <filename>/etc/yum.repos.d/</filename> ���������������������������������������������������������������������������������������������������������������</para>
<tip>
<title>���������������������</title>
<para>������������������������������ <filename>.repo</filename> ���������</para>
</tip>
<para>������������ <systemitem class="username">root</systemitem> ��������������������������������������������������������������� <filename>example.repo</filename>������������������</para>
<screen>
<userinput>su -c 'cp example.repo /etc/yum.repos.d/'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<para>��������������������������������������������� <command>gpgkey</command> ��������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� <xref linkend="sn-authorizing-package-sources"/>���</para>
<note>
<title>��������� <application>up2date</application> ������</title>
<para>��� &FED; 4 ���������<command>yum</command> ��������������������� <application>up2date</application> ������������ &FED; 3 ��������������������������������������������������� <application>up2date</application> ��������������������������������������������������� <filename>/etc/sysconfig/rhn/sources</filename>���</para>
</note>
</section>
<section id="sn-authorizing-package-sources">
<title>������������������������</title>
<indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm>
<para>������������ <command>rpm</command> ��������������������������������� <command>rpm</command> ��� <option>import</option> ������������������������ <filename>GPG-PUB-KEY.asc</filename>������������������</para>
<screen>
<userinput>su -c 'rpm --import <replaceable>GPG-PUB-KEY.asc</replaceable>'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<para>������������������������������������������������������������������������ <wordasword>www.therepository.com</wordasword> ������������ <filename>GPG-PUB-KEY.asc</filename>������������������</para>
<screen>
<userinput>su -c 'rpm --import <replaceable>http://www.therepository.com/GPG-PUB-KEY.asc</replaceable>'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������</para>
<important>
<title>��� &FED; 3 ��������� &FED; ������</title>
<para>������ &FED; 3 ������������ <command>rpm</command> ��������������� &FED; ������������������������ <command>su -c 'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora'</command>���</para>
</important>
</section>
<section id="sn-compat-repositories">
<title>���������������������</title>
<indexterm>
<primary>���������</primary>
<secondary>���������������</secondary>
</indexterm> <indexterm>
<primary>������</primary>
<secondary>���������</secondary>
</indexterm>
<para>&FEX; ������������������������ &FC; ������������������������������������������������������������ &FP; ���������������������������������������������������������������������</para>
<para>��������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� &FED; ������������������������������������</para>
<para>��������������������������������������������������������� &FP; ��������������������������������� &FP; ������������������������������������������������������������������������������������������</para>
<caution>
<title>������������������</title>
<para>���������������������������������������������������������<command>yum</command> ������������������</para>
</caution>
<para>������������������ &FED; ��������������������������������������������� &FED; ������������������������������������������������������������������ &FED; ���������</para>
<tip>
<title>������������ <command>yum</command> ������������������</title>
<para>��� <command>yum</command> 2.1 ������������������������������������������������������������ &FED; 3 ��������������������������������������������������������������� &FED; ��������������������������������������������������������������� <command>yum</command> ��������������������������������������������� <filename>repodata/</filename> ���������������</para>
</tip>
</section>
</section>
<section id="sn-yum-installing-frompackage">
<title>���������������������������������������������</title>
<indexterm>
<primary>������������</primary>
<secondary>������������</secondary>
<see>������������������������</see>
</indexterm> <indexterm>
<primary>������</primary>
<secondary>������������������������</secondary>
</indexterm>
<para>������������������������ <command>yum</command> ������������������������������������������������������������������������������������������������������������������ <option>localinstall</option> ���������������������������������������</para>
<important>
<title>���������������</title>
<para>������������������������������������������������������������������������������������������ <xref linkend="sn-authorizing-package-sources"/>���</para>
</important>
<para>������������������ <filename>tsclient-0.132-4.i386.rpm</filename>������������������</para>
<screen>
<userinput>su -c 'yum localinstall <replaceable>tsclient-0.132-4.i386.rpm</replaceable>'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������</para>
<note>
<title>���������������������������������</title>
<para>���������������������������������������������������<command>yum</command> ������������������������������</para>
</note>
<para>���������������������������������������������������<command>yum</command> ���������������������������������������������������������������������������������������������������������������������������������������������</para>
<caution>
<title>������������������������������</title>
<para>���������������������������������������������������������������������<command>yum update</command> ��������������������������������������������������������������������������������������������������� RSS ���������������������������������������������������</para>
</caution>
</section>
<section id="sn-yum-maintenance">
<title>������ <command>yum</command></title>
<para><command>yum</command> ������������������������������������������ <command>yum</command> ������������������������������������������������������������������������������������������ <command>yum</command> ������������������������������������������������</para>
<section id="sn-removing-sources">
<title>���������������������������</title>
<indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm> <indexterm>
<primary>������</primary>
<secondary>������</secondary>
</indexterm>
<para>��������������������������������� <command>enable=0</command> ������������ <command>yum</command> ���������������������<command>yum</command> ������������������������������������������������</para>
<para>���������������������������</para>
<procedure>
<step>
<para>��� <filename>/etc/yum.repos.d/</filename> ���������������������������������</para>
</step>
<step>
<para>��� <filename>/var/cache/yum/</filename> ���������������������������������������</para>
</step>
</procedure>
<!-- What with the "web of trust," removing GPG keys is not really -->
<!-- something we should encourage. Having an extra GPG key in the RPM -->
<!-- database is not a vulnerability, nor does it hamper the system in -->
<!-- any way. These are probably a couple of reasons Seth didn't build -->
<!-- this function into yum as part of "clean all," for example. Since -->
<!-- we just had several admonitions against people running the rpm -->
<!-- command on its own anyway, I would just omit this part -->
<!-- completely. [PWF] -->
<!--
<important>
<title>Remove Unneeded Public Keys</title>
<para>
If you will not be using any further packages from a provider,
remove their public key from the <command>rpm</command>
keyring using the procedure described in
<xref linkend="sn-removing-publickeys" />.
</para>
</important>
</section>
<section id="sn-removing-publickeys">
<title>Removing Public Keys</title>
<indexterm>
<primary>public keys, removing</primary>
</indexterm>
<para>
To remove a public key from the keyring you first must determine
the full name of the key, as it registered in
<command>rpm</command>. Run this command to view the details of
the public keys on the <command>rpm</command> keyring:
</para>
<screen>
<userinput>rpm -qi gpg-pubkey-*</userinput>
</screen>
<para>
Locate the heading for the relevant public key. The public key
headings follow this format:
</para>
<example id="publickey-header-format">
<title>Format of <command>rpm</command> Public Key Headers</title>
<screen>
<computeroutput>Name : gpg-pubkey Relocations: (not relocatable)
Version : 4f2a6fd2 Vendor: (none)
Release : 3f9d9d3b Build Date: Wed 15 Jun 2005 09:55:33 PM BST
Install Date: Wed 15 Jun 2005 09:55:33 PM BST Build Host: localhost
Group : Public Keys Source RPM: (none)
Size : 0 License: pubkey
Signature : (none)
Summary : gpg(Fedora Project <fedora(a)redhat.com>)
Description :</computeroutput>
</screen>
</example>
<para>
Add the <option>Version</option> and <option>Release</option>
attributes to <option>gpg-pubkey-</option> to make the complete
name of the key, in the form
<option>gpg-pubkey-Version_number-Release_number</option>. The
<command>rpm</command> identification for the &FP; public key
shown above is: <option>gpg-pubkey-4f2a6fd2-3f9d9d3b</option>.
</para>
<para>
Once you know the identification name of the key, use the
command <command>rpm <option>-e</option></command> to remove it.
To remove the &FP; public key shown above the exact command
would be:
</para>
<screen>
<userinput>su -c 'rpm -e <replaceable>gpg-pubkey-4f2a6fd2-3f9d9d3b</replaceable>'</userinput>
</screen>
<para>
Enter the password for the
<systemitem class="username">root</systemitem> account when
prompted.
</para>
-->
</section>
<section id="sn-yum-clearance">
<title>������ <command>yum</command> ������</title>
<indexterm>
<primary>yum</primary>
<secondary>������������</secondary>
</indexterm>
<para>������������������<command>yum</command> ������������������������������������������������������������������������������������������������������������������������������������������������������</para>
<screen>
<userinput>su -c 'yum clean headers'</userinput>
</screen>
<para>���������������������������������������������������</para>
<screen>
<userinput>su -c 'yum clean packages'</userinput>
</screen>
<para>��������������������� <systemitem class="username">root</systemitem> ������������������</para>
<para>������������������������������������������������������������������������������������������������������������������������</para>
</section>
</section>
<section id="sn-yum-proxy-server">
<title>��������������������������� <command>yum</command></title>
<indexterm>
<primary>���������������</primary>
</indexterm> <indexterm>
<primary>yum</primary>
<secondary>������������������������������</secondary>
</indexterm>
<para>������������������<command>yum</command> ������ HTTP ������������������������������������ <command>yum</command> HTTP ��������������� HTTP/1.1��������������������������� web ��������������������������������������������� FTP ������������������ <command>yum</command> ������ FTP ������������������<filename>squid</filename> ������������������������ HTTP/1.1 ��� FTP ������������������������</para>
<tip>
<title>������������������������ <command>yum</command></title>
<para>��������� <filename>yum.conf</filename> ������������������������������ HTTP ��������������������������� web ��������������������������������������� <command>yum</command> ������ FTP ������������������������ FTP ���������&FED; ������������������ HTTP ��� FTP���</para>
</tip>
<section id="sn-yum-proxy-server-global">
<title>���������������������������</title>
<para>��������������� <command>yum</command> ������������������������������������������ <filename>/etc/yum.conf</filename> ������������������������������������<option>proxy</option> ��������������������������������������������������� URL��������� TCP ��������������������������������������������������������������������������������� <option>proxy_username</option> ��� <option>proxy_password</option> ���������������������������</para>
<para>������������������ <command>yum</command> ��������������������� <systemitem class="systemname">mycache.mydomain.com</systemitem>������������������ 3128������������ <systemitem class="username">yum-user</systemitem>��������� <systemitem>qwerty</systemitem>���</para>
<example id="config-file-httpproxy">
<title>���������������������������������������������</title>
<screen>
<computeroutput># ��������������� - proxy server:port number
proxy=http://mycache.mydomain.com:3128
# ������ yum ���������������������
proxy_username=yum-user
proxy_password=qwerty</computeroutput>
</screen>
</example>
<note>
<title>������������</title>
<para>������������ <filename>/etc/yum.conf</filename> ���������������������������<emphasis>������</emphasis> ��������������� <command>yum</command> ���������������������������������������������</para>
</note>
</section>
<section id="sn-yum-proxy-server-peruser">
<title>������������������������������������</title>
<para>������������������������������������������������������������������������������������������������������ shell ��������������������������� <command>bash</command> shell��������������� <filename>~/.bash_profile</filename> ������������������������ <command>yum</command> ��������������������� <systemitem class="systemname">mycache.mydomain.com</systemitem>������������������ 3128���</para>
<example id="profile-script-httpproxy">
<title>���������������������������������������</title>
<screen>
<computeroutput># ������������������������������������
http_proxy="http://mycache.mydomain.com:3128"
export http_proxy</computeroutput>
</screen>
</example>
<para>��������������������������������������������������������������������� URL��������������������� <systemitem class="username">yum-user</systemitem>��������� <systemitem>qwerty</systemitem>������������������</para>
<example id="profile-script-httpproxy-withpassword">
<title>���������������������������������������������</title>
<screen>
<computeroutput># ������������������������������������������������/������
http_proxy="http://yum-user:qwerty@mycache.mydomain.com:3128"
export http_proxy</computeroutput>
</screen>
</example>
<note>
<title>������������ <option>http_proxy</option></title>
<para>������������ <command>http_proxy</command> ������ <command>curl</command> ������������������������������ <command>yum</command> ������������������������������ <command>http_proxy</command>���<command>curl</command> ���������������������������������������</para>
</note>
</section>
</section>
<!-- SE: This is at the end of the document, since it looks out of place in section 1 -->
<section id="sn-acknowledgements">
<title>������</title>
<para>Paul Frields ���������������������Timothy Murphy ��������� BETA ���������</para>
</section>
<index id="generated-index"/>
</article>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
Index: Makefile
===================================================================
RCS file: /cvs/docs/yum-software-management/Makefile,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- Makefile 18 Sep 2005 22:44:53 -0000 1.5
+++ Makefile 15 Nov 2005 14:42:32 -0000 1.6
@@ -8,7 +8,7 @@
# Copyright 2005 Tommy Reynolds, MegaCoder.com
###############################################################################
-LANGUAGES = en
+LANGUAGES = en zh_CN
DOCBASE = yum-software-management
XMLEXTRAFILES-en =
18 years, 5 months
mirror-tutorial mirror-tutorial-en.xml,1.17,1.18
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10134
Modified Files:
mirror-tutorial-en.xml
Log Message:
Fixed commands to use su, removed slightly misleading language
Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- mirror-tutorial-en.xml 11 Nov 2005 16:58:48 -0000 1.17
+++ mirror-tutorial-en.xml 15 Nov 2005 14:28:05 -0000 1.18
@@ -1275,7 +1275,7 @@
</para>
<screen>
-<userinput>yum-arch -l -s /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput>
+<userinput>su -c 'yum-arch -l -s /var/www/mirror/fedora/linux/core/&FCVER;/i386/os'</userinput>
</screen>
<para>
@@ -1295,8 +1295,7 @@
<command>yum</command> (and possibly other repository client
programs). The <command>createrepo</command> command stores
this data in a folder named <filename>repodata</filename>.
- Just as with <command>yum-arch</command>, run
- <command>createrepo</command> against the directory
+ Run <command>createrepo</command> against the directory
<emphasis>under which</emphasis> you want the
<filename>repodata</filename> directory to appear. The
<command>createrepo</command> program also searches
@@ -1310,7 +1309,7 @@
</para>
<screen>
-<userinput>createrepo /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput>
+<userinput>su -c 'createrepo /var/www/mirror/fedora/linux/core/&FCVER;/i386/os'</userinput>
</screen>
<para>
@@ -1326,7 +1325,7 @@
</para>
<screen>
-<userinput>createrepo -g Fedora/base/comps.xml /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput>
+<userinput>su -c 'createrepo -g Fedora/base/comps.xml /var/www/mirror/fedora/linux/core/&FCVER;/i386/os'</userinput>
</screen>
<para>
18 years, 5 months
yum-software-management yum-software-management-en.xml,1.48,1.49
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17177
Modified Files:
yum-software-management-en.xml
Log Message:
- Fixed bug 166122
- Revised information on Fedora repositories to mention development repositories
- Renamed "Manual Installation" section for clarity
- Updated section on proxy servers
Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- yum-software-management-en.xml 13 Oct 2005 11:34:47 -0000 1.48
+++ yum-software-management-en.xml 15 Nov 2005 00:13:03 -0000 1.49
@@ -4,7 +4,7 @@
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
-<!ENTITY BOOKID "yum-software-management-1.0.3 (2005-10-13)"> <!-- change version of manual and date here -->
+<!ENTITY BOOKID "yum-software-management-1.0.4 (2005-11-15)"> <!-- change version of manual and date here -->
<!-- Bugzilla bug number for the draft notice -->
<!ENTITY BUG-NUM "155190">
@@ -68,35 +68,45 @@
</revdescription>
</revision>
<revision>
- <revnumber>1.0.1</revnumber>
- <date>2005-08-18</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Added information on installing without repository and
- manually adding keys.
- </para>
- </revdescription>
+ <revnumber>1.0.1</revnumber>
+ <date>2005-08-18</date>
+ <authorinitials>StuartEllis</authorinitials>
+ <revdescription>
+ <para>
+ Added information on installing without repository and
+ manually adding keys.
+ </para>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>1.0.2</revnumber>
+ <date>2005-08-26</date>
+ <authorinitials>StuartEllis</authorinitials>
+ <revdescription>
+ <para>
+ Fix localinstall information.
+ </para>
+ </revdescription>
</revision>
<revision>
- <revnumber>1.0.2</revnumber>
- <date>2005-08-26</date>
- <authorinitials>StuartEllis</authorinitials>
- <revdescription>
- <para>
- Fix localinstall information.
- </para>
- </revdescription>
+ <revnumber>1.0.3</revnumber>
+ <date>2005-10-13</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Fix wording (#170584).
+ </para>
+ </revdescription>
</revision>
<revision>
- <revnumber>1.0.3</revnumber>
- <date>2005-10-13</date>
- <authorinitials>PaulWFrields</authorinitials>
- <revdescription>
- <para>
- Fix wording (#170584).
- </para>
- </revdescription>
+ <revnumber>1.0.4</revnumber>
+ <date>2005-11-15</date>
+ <authorinitials>StuartEllis</authorinitials>
+ <revdescription>
+ <para>
+ Updated section on proxy servers. Fixed #166122.
+ </para>
+ </revdescription>
</revision>
</revhistory>
</articleinfo>
@@ -184,12 +194,11 @@
<section id="sn-yum-additional-resources">
<title>Additional Resources</title>
<indexterm>
- <primary>yum</primary>
- <secondary>documentation</secondary>
- </indexterm>
- <indexterm>
- <primary>yum</primary>
- <secondary>man pages</secondary>
+ <primary>yum</primary>
+ <secondary>documentation</secondary>
+ </indexterm> <indexterm>
+ <primary>yum</primary>
+ <secondary>man pages</secondary>
</indexterm>
<para>
The <command>yum</command> utility has features and options not
@@ -203,19 +212,12 @@
man yum.conf</userinput>
</screen>
<indexterm>
- <primary>yum</primary>
- <secondary>web sites</secondary>
- </indexterm>
- <indexterm>
- <primary>yum</primary>
- <secondary>mailing lists</secondary>
+ <primary>yum</primary>
+ <secondary>web sites</secondary>
+ </indexterm> <indexterm>
+ <primary>yum</primary>
+ <secondary>mailing lists</secondary>
</indexterm>
-<!-- Hopefully this is not too confusing below. This is sort of a -->
-<!-- grammar/usage issue. If you use a variablelist, you don't want to -->
-<!-- use sentences, but rather headings, in the term area. Alternately, -->
-<!-- if you like sentences, just use a para instead for the whole -->
-<!-- collection of links. [PWF] -->
-<!-- SE: Multiple links in a paragraph is pretty ugly. Not that I like this layout either :) -->
<para>
Other useful <command>yum</command> resources on the Internet
include:
@@ -255,6 +257,17 @@
</listitem>
</varlistentry>
</variablelist>
+ <tip>
+ <title>Check &BZ; First</title>
+ <para>
+ If you encounter a persistent error with a specific operation,
+ visit &BZ-URL; and review the bug reports for the package or
+ packages involved. An error in a package may cause all
+ <command>yum</command> operations that rely on that package to
+ fail. Please file bug reports for &FED; packages, including
+ <command>yum</command>, on this &BZ; web site.
+ </para>
+ </tip>
</section>
</section>
@@ -264,8 +277,8 @@
<section id="sn-about-packages">
<title>About Packages</title>
<indexterm>
- <primary>packages</primary>
- <secondary>defined</secondary>
+ <primary>packages</primary>
+ <secondary>defined</secondary>
</indexterm>
<para>
&FED; software and documentation is supplied in the form of
@@ -287,13 +300,23 @@
the public keys for approved package sources. The system
administrator configures these approved package sources.
</para>
+
+ <note>
+ <title>All &FED; Packages are Open Source Software</title>
+
+ <para>
+ All of the software provided by the &FP; is open source
+ software. You may download and install &FED; packages on as
+ many systems as desired.
+ </para>
+ </note>
</section>
<section id="sn-about-repositories">
<title>About Repositories</title>
<indexterm>
- <primary>repositories</primary>
- <secondary>defined</secondary>
+ <primary>repositories</primary>
+ <secondary>defined</secondary>
</indexterm>
<para>
A <firstterm>repository</firstterm> is a prepared directory or
@@ -307,48 +330,71 @@
</para>
<para>
- The package management utilities in &FC; are already configured
- to use a network of servers that provide three repositories:
+ A network of servers provide several repositories for each
+ version of &FED;. The package management utilities in &FC; are
+ already configured to use three of these repositories:
</para>
- <itemizedlist>
- <listitem>
- <para>
- The packages that make up &FC;, as it is released on disc
- </para>
- </listitem>
- <listitem>
- <para>
- Updated versions of &FC; software
- </para>
- </listitem>
- <listitem>
- <para>
- A large selection of additional software, known as &FEX;
- </para>
- </listitem>
- </itemizedlist>
+ <variablelist>
+ <varlistentry>
+ <term>
+ Base
+ </term>
+ <listitem>
+ <para>
+ The packages that make up a &FC; release, as it is on disc
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ Updates
+ </term>
+ <listitem>
+ <para>
+ Updated versions of packages that are provided in Base
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ &EX;
+ </term>
+ <listitem>
+ <para>
+ Packages for a large selection of additional software
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
<note>
<title>Previous Versions of &FED;</title>
<para>
- &FED; &FCLOCALVER; automatically supports all three
- repositories. You must manually configure &FED; 3 systems to
- use &FEX;, as noted in
+ &FED; &FCLOCALVER; automatically supports the three
+ repositories listed above. You must manually configure &FED; 3
+ systems to use &FEX;, as noted in
<xref linkend="sn-using-repositories"/>.
</para>
</note>
- <note>
- <title>All &FED; Packages are Open Source Software</title>
+ <warning>
+ <title>&FED; Development Repositories</title>
<para>
- 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.
+ &FC; 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 &FED; software:
+ <filename>fedora-devel</filename> (Rawhide),
+ <filename>fedora-extras-devel</filename>, and
+ <filename>updates-testing</filename>.
</para>
- </note>
+ </warning>
<para>
Third-party software developers also provide repositories for
@@ -357,8 +403,8 @@
<xref linkend="sn-using-repositories"/>.
</para>
<indexterm>
- <primary>package groups</primary>
- <secondary>defined</secondary>
+ <primary>package groups</primary>
+ <secondary>defined</secondary>
</indexterm>
<para>
You may also use the <firstterm>package groups</firstterm>
@@ -408,8 +454,8 @@
<section id="sn-about-dependencies">
<title>About Dependencies</title>
<indexterm>
- <primary>dependencies</primary>
- <secondary>defined</secondary>
+ <primary>dependencies</primary>
+ <secondary>defined</secondary>
</indexterm>
<para>
Some of the files installed on a &FED; distribution are
@@ -436,17 +482,16 @@
<section id="sn-package-names">
<title>Understanding Package Names</title>
<indexterm>
- <primary>packages</primary>
- <secondary>hardware compatibility</secondary>
- </indexterm>
- <indexterm>
- <primary>packages</primary>
- <secondary>naming</secondary>
+ <primary>packages</primary>
+ <secondary>hardware compatibility</secondary>
+ </indexterm> <indexterm>
+ <primary>packages</primary>
+ <secondary>naming</secondary>
</indexterm>
<para>
Each package file has a long name that indicates several key
- pieces of information. This is the full name of the
- <filename>tsclient</filename> package supplied with &FC;:
+ pieces of information. For example, this is the full name of a
+ <filename>tsclient</filename> package:
</para>
<screen>
<filename>tsclient-0.132-6.i386.rpm</filename>
@@ -582,18 +627,16 @@
<section id="sn-software-management-tools">
<title>Software Management Tools in &FC;</title>
<indexterm>
- <primary>Add/Remove Applications utility</primary>
- </indexterm>
- <indexterm>
- <primary>Alert Icon</primary>
- </indexterm>
- <indexterm>
- <primary>up2date</primary>
+ <primary>Add/Remove Applications utility</primary>
+ </indexterm> <indexterm>
+ <primary>Alert Icon</primary>
+ </indexterm> <indexterm>
+ <primary>up2date</primary>
</indexterm>
<para>
The <command>yum</command> utility is a complete software
- management system. &FC; also includes several other
- applications that can supplement <command>yum</command>.
+ management system. &FC; also includes several other applications
+ that can supplement <command>yum</command>.
</para>
<para>
@@ -644,8 +687,8 @@
<section id="sn-managing-packages">
<title>Managing Software with <command>yum</command></title>
<indexterm>
- <primary>yum</primary>
- <secondary>software management</secondary>
+ <primary>yum</primary>
+ <secondary>software management</secondary>
</indexterm>
<para>
Use the <command>yum</command> utility to modify the software on
@@ -778,7 +821,7 @@
<para>
Check the public key, and then press <keycap>y</keycap> to import
the key and authorize the key for use. If you press
- <keycap>N</keycap> or <keycap>Enter</keycap> ,
+ <keycap>N</keycap> or <keycap>Enter</keycap>,
<command>yum</command> stops without installing any packages.
</para>
@@ -789,6 +832,13 @@
packages required for the transaction are successfully downloaded
and verified, <command>yum</command> applies them to your system.
</para>
+
+ <para>
+ Every completed transaction records the affected packages in the
+ log file <filename>/var/log/yum.log</filename>. You may only read
+ this file with <systemitem class="username">root</systemitem>
+ access.
+ </para>
<tip>
<title>Downloads are Cached</title>
<para>
@@ -803,12 +853,11 @@
<section id="sn-yum-installing-withrepositories">
<title>Installing New Software with <command>yum</command></title>
<indexterm>
- <primary>installing software</primary>
- <see>software, installing</see>
- </indexterm>
- <indexterm>
- <primary>software</primary>
- <secondary>installing</secondary>
+ <primary>installing software</primary>
+ <see>software, installing</see>
+ </indexterm> <indexterm>
+ <primary>software</primary>
+ <secondary>installing</secondary>
</indexterm>
<para>
To install the package <filename>tsclient</filename>, enter the
@@ -854,12 +903,11 @@
<section id="sn-yum-updating-withrepositories">
<title>Updating Software with <command>yum</command></title>
<indexterm>
- <primary>updating</primary>
- <secondary>software packages</secondary>
- </indexterm>
- <indexterm>
- <primary>software</primary>
- <secondary>updating</secondary>
+ <primary>updating</primary>
+ <secondary>software packages</secondary>
+ </indexterm> <indexterm>
+ <primary>software</primary>
+ <secondary>updating</secondary>
</indexterm>
<para>
To update the <filename>tsclient</filename> package to the
@@ -913,11 +961,10 @@
<section id="sn-yum-removing-software">
<title>Removing Software with <command>yum</command></title>
<indexterm>
- <primary>removing software</primary>
- </indexterm>
- <indexterm>
- <primary>software</primary>
- <secondary>removing</secondary>
+ <primary>removing software</primary>
+ </indexterm> <indexterm>
+ <primary>software</primary>
+ <secondary>removing</secondary>
</indexterm>
<para>
To remove software, <command>yum</command> examines your system
@@ -968,12 +1015,11 @@
<section id="sn-searching-packages">
<title>Searching for Packages with <command>yum</command></title>
<indexterm>
- <primary>packages</primary>
- <secondary>locating</secondary>
- </indexterm>
- <indexterm>
- <primary>searching</primary>
- <secondary>for packages</secondary>
+ <primary>packages</primary>
+ <secondary>locating</secondary>
+ </indexterm> <indexterm>
+ <primary>searching</primary>
+ <secondary>for packages</secondary>
</indexterm>
<para>
Use the search features of <command>yum</command> to find software
@@ -1126,12 +1172,11 @@
<section id="sn-updating-your-system">
<title>Updating Your System with <command>yum</command></title>
<indexterm>
- <primary>updating</primary>
- <secondary>full system</secondary>
- </indexterm>
- <indexterm>
- <primary>yum</primary>
- <secondary>updating full system</secondary>
+ <primary>updating</primary>
+ <secondary>full system</secondary>
+ </indexterm> <indexterm>
+ <primary>yum</primary>
+ <secondary>updating full system</secondary>
</indexterm>
<para>
Use the <option>update</option> option to upgrade all of your
@@ -1153,7 +1198,7 @@
<section id="sn-automatic-updating">
<title>Automatically Updating Your System</title>
<indexterm>
- <primary>automatic updating</primary>
+ <primary>automatic updating</primary>
</indexterm>
<para>
The <filename>yum</filename> package supplied with &FC; includes
@@ -1187,15 +1232,13 @@
<section id="sn-using-repositories">
<title>Using Other Software Repositories</title>
<indexterm>
- <primary>&FEX;</primary>
- </indexterm>
- <indexterm>
- <primary>repositories</primary>
- <secondary>finding</secondary>
- </indexterm>
- <indexterm>
- <primary>searching</primary>
- <secondary>for repositories</secondary>
+ <primary>&FEX;</primary>
+ </indexterm> <indexterm>
+ <primary>repositories</primary>
+ <secondary>finding</secondary>
+ </indexterm> <indexterm>
+ <primary>searching</primary>
+ <secondary>for repositories</secondary>
</indexterm>
<para>
&FED; systems automatically use the &FP; repositories. These
@@ -1230,8 +1273,8 @@
<section id="sn-adding-repositories">
<title>Adding a Repository as a Package Source</title>
<indexterm>
- <primary>repositories</primary>
- <secondary>adding to yum</secondary>
+ <primary>repositories</primary>
+ <secondary>adding to yum</secondary>
</indexterm>
<para>
To add an extra repository, place a definition file in the
@@ -1287,8 +1330,8 @@
<section id="sn-authorizing-package-sources">
<title>Manually Authorizing Package Sources</title>
<indexterm>
- <primary>public keys</primary>
- <secondary>adding</secondary>
+ <primary>public keys</primary>
+ <secondary>adding</secondary>
</indexterm>
<para>
To manually add a public key to your <command>rpm</command>
@@ -1334,12 +1377,11 @@
<section id="sn-compat-repositories">
<title>Understanding Repository Compatibility</title>
<indexterm>
- <primary>packages</primary>
- <secondary>software compatibility</secondary>
- </indexterm>
- <indexterm>
- <primary>repositories</primary>
- <secondary>compatibility</secondary>
+ <primary>packages</primary>
+ <secondary>software compatibility</secondary>
+ </indexterm> <indexterm>
+ <primary>repositories</primary>
+ <secondary>compatibility</secondary>
</indexterm>
<para>
The &FEX; repository provides packages which are built to the
@@ -1394,6 +1436,78 @@
</section>
</section>
+ <section id="sn-yum-installing-frompackage">
+ <title>Installing Software from an Isolated Package</title>
+ <indexterm>
+ <primary>installing software</primary>
+ <secondary>from a package</secondary>
+ <see>software, installing from a package</see>
+ </indexterm> <indexterm>
+ <primary>software</primary>
+ <secondary>installing from a package</secondary>
+ </indexterm>
+ <para>
+ Use repositories and the standard <command>yum</command> commands
+ to locate and install new software, unless the software package is
+ not available from any repository. In these cases, use the
+ <option>localinstall</option> function to install the software
+ from the package file.
+ </para>
+
+ <important>
+ <title>Public Key is Required</title>
+
+ <para>
+ Ensure that the public key for the package source has been
+ imported before you install a package without a repository.
+ Refer to <xref linkend="sn-authorizing-package-sources"/>.
+ </para>
+ </important>
+
+ <para>
+ Enter this command to install the package
+ <filename>tsclient-0.132-4.i386.rpm</filename>:
+ </para>
+<screen>
+<userinput>su -c 'yum localinstall <replaceable>tsclient-0.132-4.i386.rpm</replaceable>'</userinput>
+</screen>
+ <para>
+ At the prompt, enter the
+ <systemitem
+ class="username">root</systemitem> password.
+ </para>
+
+ <note>
+ <title>Previously Installed Software is Updated</title>
+
+ <para>
+ If the package provides a later version of software that is
+ already installed on your system, <command>yum</command> updates
+ the installed software.
+ </para>
+ </note>
+
+ <para>
+ If the package requires software that is not installed on your
+ system, <command>yum</command> attempts to meet the dependencies
+ with packages from the configured repositories. You may need to
+ manually download and install additional packages in order to
+ satisfy all of the dependencies.
+ </para>
+
+ <caution>
+ <title>Maintaining Manually Installed Software</title>
+
+ <para>
+ If you install software that is not provided by a repository,
+ <command>yum update</command> cannot automatically upgrade it as
+ new versions become available. To ensure that you have the
+ latest packages, subscribe to e-mail or RSS services that notify
+ you when new versions are released.
+ </para>
+ </caution>
+ </section>
+
<section id="sn-yum-maintenance">
<title>Maintaining <command>yum</command></title>
@@ -1409,12 +1523,11 @@
<section id="sn-removing-sources">
<title>Disabling or Removing Package Sources</title>
<indexterm>
- <primary>repositories</primary>
- <secondary>disabling in yum</secondary>
- </indexterm>
- <indexterm>
- <primary>repositories</primary>
- <secondary>removing from yum</secondary>
+ <primary>repositories</primary>
+ <secondary>disabling in yum</secondary>
+ </indexterm> <indexterm>
+ <primary>repositories</primary>
+ <secondary>removing from yum</secondary>
</indexterm>
<para>
Set <command>enable=0</command> in a definition file to prevent
@@ -1526,8 +1639,8 @@
<section id="sn-yum-clearance">
<title>Clearing the <command>yum</command> Caches</title>
<indexterm>
- <primary>yum</primary>
- <secondary>cleaning caches</secondary>
+ <primary>yum</primary>
+ <secondary>cleaning caches</secondary>
</indexterm>
<para>
By default, <command>yum</command> retains the packages and
@@ -1558,114 +1671,61 @@
</section>
</section>
-<!-- SE: The sections below are important, but only for certain situations - they do not represent the normal use of yum. Perhaps they should be explicitly marked as appendices ? -->
-
- <section id="sn-yum-installing-frompackage">
- <title>Manually Installing Software</title>
- <indexterm>
- <primary>installing software</primary>
- <secondary>from a package</secondary>
- <see>software, installing from a package</see>
- </indexterm>
+ <section id="sn-yum-proxy-server">
+ <title>Using <command>yum</command> with a Proxy Server</title>
<indexterm>
- <primary>software</primary>
- <secondary>installing from a package</secondary>
+ <primary>proxy server</primary>
+ </indexterm> <indexterm>
+ <primary>yum</primary>
+ <secondary>using with a proxy server</secondary>
</indexterm>
<para>
- Use repositories and the standard <command>yum</command> commands
- to locate and install new software, unless the software package is
- not available from any repository. In these cases, use the
- <option>localinstall</option> function to install the software
- from the package file.
+ By default, <command>yum</command> accesses network repositories
+ with HTTP. All <command>yum</command> HTTP operations use
+ HTTP/1.1, and are compatible with web proxy servers that support
+ this standard. You may also access FTP repositories, and configure
+ <command>yum</command> to use an FTP proxy server. The
+ <filename>squid</filename> package provides a proxy service for
+ both HTTP/1.1 and FTP connections.
</para>
-
- <important>
- <title>Public Key is Required</title>
-
+ <tip>
+ <title>Modifying <command>yum</command> for Network Compatibility</title>
<para>
- Ensure that the public key for the package source has been
- imported before you install a package without a repository.
- Refer to <xref linkend="sn-authorizing-package-sources"/>.
+ Refer to the <command>man</command> page for
+ <filename>yum.conf</filename> for information on HTTP settings
+ that may be modified for compatibility with nonstandard web
+ proxy servers. Alternatively, configure <command>yum</command>
+ to use an FTP proxy server, and access repositories that support
+ FTP. The &FED; repositories support both HTTP and FTP.
</para>
- </important>
-
- <para>
- Enter this command to install the package
- <filename>tsclient-0.132-4.i386.rpm</filename>:
- </para>
-<screen>
-<userinput>su -c 'yum localinstall <replaceable>tsclient-0.132-4.i386.rpm</replaceable>'</userinput>
-</screen>
- <para>
- At the prompt, enter the
- <systemitem
- class="username">root</systemitem> password.
- </para>
-
- <note>
- <title>Previously Installed Software is Updated</title>
+ </tip>
+ <section id="sn-yum-proxy-server-global">
+ <title>Configuring Proxy Server Access</title>
<para>
- If the package provides a later version of software that is
- already installed on your system, <command>yum</command> updates
- the installed software.
+ To enable all <command>yum</command> operations to use a proxy
+ server, specify the proxy server details in
+ <filename>/etc/yum.conf</filename>. The <option>proxy</option>
+ setting must specify the proxy server as a complete URL,
+ including the TCP port number. If your proxy server requires a
+ username and password, specify these by adding
+ <option>proxy_username</option> and
+ <option>proxy_password</option> settings.
</para>
- </note>
-
- <para>
- If the package requires software that is not installed on your
- system, <command>yum</command> attempts to meet the dependencies
- with packages from the configured repositories. You may need to
- manually download and install additional packages in order to
- satisfy all of the dependencies.
- </para>
-
- <caution>
- <title>Maintaining Manually Installed Software</title>
<para>
- If you install software that is not provided by a repository,
- <command>yum update</command> cannot automatically upgrade it as
- new versions become available. To ensure that you have the
- latest packages, subscribe to e-mail or RSS services that notify
- you when new versions are released.
- </para>
- </caution>
- </section>
-
- <section id="sn-yum-proxy-server">
- <title>Using <command>yum</command> with a Proxy Server</title>
- <indexterm>
- <primary>proxy server</primary>
- </indexterm>
- <indexterm>
- <primary>yum</primary>
- <secondary>using with a proxy server</secondary>
- </indexterm>
- <para>
- You may access repositories through standard web proxy servers. If
- your system accesses the Internet through a web proxy server,
- specify the proxy server details in
- <filename>/etc/yum.conf</filename>. The <option>proxy</option>
- setting must specify the proxy server as a complete URL, including
- the TCP port number. If your proxy server requires a username and
- password, specify these by adding <option>proxy_username</option>
- and <option>proxy_password</option> settings.
- </para>
-
- <para>
- The settings below enable <command>yum</command> to use the proxy
- server
- <systemitem
+ The settings below enable <command>yum</command> to use the
+ proxy server
+ <systemitem
class="systemname">mycache.mydomain.com</systemitem>,
- connecting to port 3128, with the username
- <systemitem
+ connecting to port 3128, with the username
+ <systemitem
class="username">yum-user</systemitem> and the
- password <systemitem>qwerty</systemitem>.
- </para>
+ password <systemitem>qwerty</systemitem>.
+ </para>
- <example id="config-file-httpproxy">
- <title>Configuration File Settings for Using A Proxy Server</title>
+ <example id="config-file-httpproxy">
+ <title>Configuration File Settings for Using A Proxy Server</title>
<screen>
<computeroutput># The proxy server - proxy server:port number
proxy=http://mycache.mydomain.com:3128
@@ -1673,67 +1733,72 @@
proxy_username=yum-user
proxy_password=qwerty</computeroutput>
</screen>
- </example>
+ </example>
- <note>
- <title>Global Settings</title>
+ <note>
+ <title>Global Settings</title>
- <para>
- If you define a proxy server in
- <filename>/etc/yum.conf</filename>, <emphasis>all</emphasis>
- users connect to the proxy server with those details when using
- <command>yum</command>.
- </para>
- </note>
+ <para>
+ If you define a proxy server in
+ <filename>/etc/yum.conf</filename>, <emphasis>all</emphasis>
+ users connect to the proxy server with those details when
+ using <command>yum</command>.
+ </para>
+ </note>
+ </section>
- <para>
- To enable proxy access for a specific user, add the lines in the
- example box below to the user's shell profile. For the default
- <command>bash</command> shell, the profile is the file
- <filename>~/.bash_profile</filename>. The settings below enable
- <command>yum</command> to use the proxy server
- <systemitem
+ <section id="sn-yum-proxy-server-peruser">
+ <title>Configuring Proxy Server Access for a Single User</title>
+
+ <para>
+ To enable proxy access for a specific user, add the lines in the
+ example box below to the user's shell profile. For the default
+ <command>bash</command> shell, the profile is the file
+ <filename>~/.bash_profile</filename>. The settings below enable
+ <command>yum</command> to use the proxy server
+ <systemitem
class="systemname">mycache.mydomain.com</systemitem>,
- connecting to port 3128.
- </para>
+ connecting to port 3128.
+ </para>
- <example id="profile-script-httpproxy">
- <title>Profile Settings for Using a Proxy Server</title>
+ <example id="profile-script-httpproxy">
+ <title>Profile Settings for Using a Proxy Server</title>
<screen>
<computeroutput># The Web proxy server used by this account
http_proxy="http://mycache.mydomain.com:3128"
export http_proxy</computeroutput>
</screen>
- </example>
+ </example>
- <para>
- If the proxy server requires a username and password, add these to
- the URL. To include the username
- <systemitem class="username">yum-user</systemitem> and the
- password <systemitem>qwerty</systemitem>, add these settings:
- </para>
+ <para>
+ If the proxy server requires a username and password, add these
+ to the URL. To include the username
+ <systemitem class="username">yum-user</systemitem> and the
+ password <systemitem>qwerty</systemitem>, add these settings:
+ </para>
- <example id="profile-script-httpproxy-withpassword">
- <title>Profile Settings for a Secured Proxy Server</title>
+ <example id="profile-script-httpproxy-withpassword">
+ <title>Profile Settings for a Secured Proxy Server</title>
<screen>
<computeroutput># The Web proxy server, with the username and password for this account
http_proxy="http://yum-user:qwerty@mycache.mydomain.com:3128"
export http_proxy</computeroutput>
</screen>
- </example>
+ </example>
- <note>
- <title>The <option>http_proxy</option> Environment Variable</title>
+ <note>
+ <title>The <option>http_proxy</option> Environment Variable</title>
- <para>
- The <command>http_proxy</command> environment variable is also
- used by <command>curl</command> and other utilities. Although
- <command>yum</command> itself may use
- <command>http_proxy</command> in either upper-case or
- lower-case, <command>curl</command> requires the name of the
- variable to be in lower-case.
- </para>
- </note>
+ <para>
+ The <command>http_proxy</command> environment variable is also
+ used by <command>curl</command> and other utilities. Although
+ <command>yum</command> itself may use
+ <command>http_proxy</command> in either upper-case or
+ lower-case, <command>curl</command> requires the name of the
+ variable to be in lower-case.
+ </para>
+ </note>
+ </section>
</section>
<!-- SE: This is at the end of the document, since it looks out of place in section 1 -->
18 years, 5 months
rpm-guide rpm-guide-advanced-packaging-en.xml, 1.4, 1.5 rpm-guide-creating-rpms-en.xml, 1.4, 1.5 rpm-guide-intro-packaging-en.xml, 1.4, 1.5 rpm-guide-other-os-en.xml, 1.4, 1.5 rpm-guide-package-structure-en.xml, 1.2, 1.3 rpm-guide-programming-c-en.xml, 1.4, 1.5 rpm-guide-rpmbuild-en.xml, 1.4, 1.5 rpm-guide-specfile-syntax-en.xml, 1.3, 1.4 rpm-guide-specfiles-en.xml, 1.4, 1.5 rpm-guide-transactions-en.xml, 1.4, 1.5 rpm-guide-using-rpm-en.xml, 1.4, 1.5
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11082
Modified Files:
rpm-guide-advanced-packaging-en.xml
rpm-guide-creating-rpms-en.xml
rpm-guide-intro-packaging-en.xml rpm-guide-other-os-en.xml
rpm-guide-package-structure-en.xml
rpm-guide-programming-c-en.xml rpm-guide-rpmbuild-en.xml
rpm-guide-specfile-syntax-en.xml rpm-guide-specfiles-en.xml
rpm-guide-transactions-en.xml rpm-guide-using-rpm-en.xml
Log Message:
Completed replacement of "Chapter X" with links
Index: rpm-guide-advanced-packaging-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-advanced-packaging-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-advanced-packaging-en.xml 10 Nov 2005 22:30:06 -0000 1.4
+++ rpm-guide-advanced-packaging-en.xml 14 Nov 2005 21:55:05 -0000 1.5
@@ -1356,9 +1356,7 @@
Cross Reference
</para>
<para>
- See <xref linkend="ch-customizing-rpm"/> for more on macro file locations, and Chapters 19
- and 20 for more on using RPM on other versions of Linux and other
- operating systems, respectively.
+ See <xref linkend="ch-customizing-rpm"/> for more on macro file locations, and <xref linkend="ch-other-linuxes"/> and <xref linkend="ch-other-os"/> for more on using RPM on other versions of Linux and other operating systems, respectively.
</para>
<para>
RPM supports a number of ways to make parts of your spec file
Index: rpm-guide-creating-rpms-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-creating-rpms-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-creating-rpms-en.xml 10 Nov 2005 22:30:06 -0000 1.4
+++ rpm-guide-creating-rpms-en.xml 14 Nov 2005 21:55:05 -0000 1.5
@@ -1095,7 +1095,7 @@
This example skips the install and uninstall script sections,
as well as a verification section. There are also no triggers
defined in this RPM spec file. All of these topics are covered
- in Chapters 10 and 11.
+ in <xref linkend="ch-specfiles"/> and <xref linkend="ch-advanced-packaging"/>.
</para>
<para>
Once you have written your spec file, and placed the files in
@@ -1552,8 +1552,7 @@
<sect1>
<title>Verifying Your RPMS</title>
<para>
- After you've built an RPM, you can use the techniques from Chapter
- 5 to verify the RPM. You can also use the ���bl option to the
+ After you've built an RPM, you can use the techniques from <xref linkend="ch-using-rpm-db"/> to verify the RPM. You can also use the ���bl option to the
rpmbuild command to verify the list of files in the RPM. Use a
command like the following:
</para>
Index: rpm-guide-intro-packaging-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-intro-packaging-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-intro-packaging-en.xml 31 Oct 2005 23:18:20 -0000 1.4
+++ rpm-guide-intro-packaging-en.xml 14 Nov 2005 21:55:05 -0000 1.5
@@ -402,7 +402,7 @@
<title>Change of Name</title>
<!-- SE: Don't replace "&RH;" with an entity here: we don't want the text to change -->
<para>
- RPM was originally called &RH; Package Manager. After
+ RPM was originally called Red Hat Package Manager. After
adoption by other Linux distributions, the name has changed to
simply the RPM Package Manager. The RPM initials remain the
same.
@@ -411,11 +411,11 @@
<para>
As the original name implies, RPM was developed by &FORMAL-RHI;,
the major Linux distributor in the United States. Even though the
- original name seems to point to a &RH;-only solution, most Linux
+ original name seems to point to a Red Hat-only solution, most Linux
distributions use the RPM software. The RPM software provides a
foundation needed by Linux system administrators throughout the
world. You can even use RPM on other operating systems, both Linux
- and non-Linux, as covered in Chapters 19 and 20, respectively.
+ and non-Linux, as covered in <xref linkend="ch-other-linuxes"/> and <xref linkend="ch-other-os"/>, respectively.
</para>
<para>
The RPM system provides all of the features needed to manage
Index: rpm-guide-other-os-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-other-os-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-other-os-en.xml 10 Nov 2005 22:30:07 -0000 1.4
+++ rpm-guide-other-os-en.xml 14 Nov 2005 21:55:05 -0000 1.5
@@ -1234,8 +1234,7 @@
Cross Reference
</para>
<para>
- <xref linkend="ch-creating-rpms"/> covers how to run the rpmbuild command, and Chapter
- 10 covers spec files in detail.
+ <xref linkend="ch-creating-rpms"/> covers how to run the rpmbuild command, and <xref linkend="ch-specfiles"/> covers spec files in detail.
</para>
</sect3>
<sect3>
Index: rpm-guide-package-structure-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-package-structure-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-package-structure-en.xml 26 Oct 2005 01:54:11 -0000 1.2
+++ rpm-guide-package-structure-en.xml 14 Nov 2005 21:55:05 -0000 1.3
@@ -34,8 +34,7 @@
Cross Reference
</para>
<para>
- Chapters 16, 17, and 18 cover programming with C, Python, and Perl,
- respectively.
+ <xref linkend="ch-programming-c"/>, <xref linkend="ch-rpm-programming-python"/>, and <xref linkend="ch-programming-perl"/> cover programming with C, Python, and Perl, respectively.
</para>
<para>
The RPM package format described here has been standardized as part
Index: rpm-guide-programming-c-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-c-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-programming-c-en.xml 10 Nov 2005 22:30:07 -0000 1.4
+++ rpm-guide-programming-c-en.xml 14 Nov 2005 21:55:05 -0000 1.5
@@ -2176,8 +2176,7 @@
</para>
<para>
All in all, the popt library provides a handy library for
- processing command-line options and aliases, covered in Chapter
- 21.
+ processing command-line options and aliases, covered in <xref linkend="ch-customizing-rpm"/>.
</para>
</sect2>
<sect2>
Index: rpm-guide-rpmbuild-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-rpmbuild-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-rpmbuild-en.xml 10 Nov 2005 22:30:07 -0000 1.4
+++ rpm-guide-rpmbuild-en.xml 14 Nov 2005 21:55:05 -0000 1.5
@@ -45,8 +45,7 @@
<title>Building RPMs with the rpmbuild Command</title>
<para>
The rpmbuild command provides a workhorse command for building
- RPMs in all sorts of ways. The basic syntax, as shown in Chapter
- 9, is:
+ RPMs in all sorts of ways. The basic syntax, as shown in <xref linkend="ch-creating-rpms"/>, is:
</para>
<para>
rpmbuild -bBuildStage spec_file
Index: rpm-guide-specfile-syntax-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfile-syntax-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-specfile-syntax-en.xml 10 Nov 2005 22:30:07 -0000 1.3
+++ rpm-guide-specfile-syntax-en.xml 14 Nov 2005 21:55:05 -0000 1.4
@@ -662,7 +662,7 @@
<title>Build Sections</title>
<para>
After providing information about the package, you need to define
- the build stages, as described in Chapters 10 and 12.
+ the build stages, as described in <xref linkend="ch-specfiles"/> and <xref linkend="ch-rpmbuild"/>.
</para>
<sect2>
<title>Build preparation</title>
Index: rpm-guide-specfiles-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfiles-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-specfiles-en.xml 10 Nov 2005 22:30:07 -0000 1.4
+++ rpm-guide-specfiles-en.xml 14 Nov 2005 21:55:05 -0000 1.5
@@ -196,9 +196,10 @@
<sect2>
<title>Storing spec files on disk</title>
<para>
- As discussed in <xref linkend="ch-creating-rpms"/> , the rpmbuild command expands source
- RPMs to the /usr/src/redhat directory. Under this directory, the
- RPM system assumes five subdirectories, listed in Table 10-1.
+ As discussed in <xref linkend="ch-creating-rpms"/> , the
+ rpmbuild command expands source RPMs to the /usr/src/redhat
+ directory. Under this directory, the RPM system assumes five
+ subdirectories, listed in Table 10-1.
</para>
<para>
Table 10-1 Default RPM directories
@@ -291,11 +292,13 @@
Cross Reference
</para>
<para>
- These directories are the default directories. See <xref linkend="ch-specfile-syntax"/>
- for changing RPM default values. In addition, these are the
- defaults for &RHL;. See Chapters 19 and 20 for
- discussions on other versions of Linux and other non-Linux
- operating systems, respectively.
+ These directories are the default directories. See
+ <xref linkend="ch-specfile-syntax"/> for changing RPM default
+ values. In addition, these are the defaults for &RHL;. See
+ <xref linkend="ch-other-linuxes"/> and
+ <xref linkend="ch-other-linuxes"/> for discussions on other
+ versions of Linux and other non-Linux operating systems,
+ respectively.
</para>
<para>
With the knowledge of the spec file syntax covered in the
@@ -432,15 +435,15 @@
<para>
Many graphical installation tools divide packages by these
categories, so you want to fit into the existing group names
- if possible. (See <xref linkend="ch-using-rpm-db"/> for more on querying group
- information from RPMs.) The official list of groups are
- located in the file /usr/share/doc/rpm-4.1/GROUPS for RPM 4.1,
- and in a similar location for other RPM versions.
+ if possible. (See <xref linkend="ch-using-rpm-db"/> for more
+ on querying group information from RPMs.) The official list of
+ groups are located in the file /usr/share/doc/rpm-4.1/GROUPS
+ for RPM 4.1, and in a similar location for other RPM versions.
</para>
<para>
The Distribution: directive is used by Linux distribution
- vendors such as &RH; to identify that the package is part
- of a given distribution, or was built for a particular
+ vendors such as &RH; to identify that the package is part of a
+ given distribution, or was built for a particular
distribution. Most packages created outside of the Linux
vendors don���t provide this directive.
</para>
@@ -615,8 +618,9 @@
Cross Reference
</para>
<para>
- Chapters 19 and 20 cover RPMs on other versions of Linux and
- other operating systems, respectively.
+ <xref linkend="ch-other-linuxes"/> and
+ <xref linkend="ch-other-os"/> cover RPMs on other versions of
+ Linux and other operating systems, respectively.
</para>
</sect3>
</sect2>
@@ -822,8 +826,9 @@
Cross Reference
</para>
<para>
- <xref linkend="ch-packaging-guidelines"/> discusses packaging guidelines and best practices.
- Starting from pristine sources is one of the best practices.
+ <xref linkend="ch-packaging-guidelines"/> discusses packaging
+ guidelines and best practices. Starting from pristine sources is
+ one of the best practices.
</para>
<para>
Similar to the sources directives, you can define a Nopatch:
@@ -849,7 +854,8 @@
Cross Reference
</para>
<para>
- <xref linkend="ch-creating-rpms"/> covers make and other Linux build tools.
+ <xref linkend="ch-creating-rpms"/> covers make and other Linux
+ build tools.
</para>
<para>
In RPM terms, building the package is split into four steps:
@@ -1215,8 +1221,8 @@
</para>
<para>
If you intend to support relocatable packages, covered in
- <xref linkend="ch-advanced-packaging"/> , you will likely need to pass a --prefix option to
- the configure script. For example:
+ <xref linkend="ch-advanced-packaging"/> , you will likely need
+ to pass a --prefix option to the configure script. For example:
</para>
<para>
%build
@@ -1370,8 +1376,9 @@
Cross Reference
</para>
<para>
- <xref linkend="ch-advanced-packaging"/> covers triggers, another form of script that gets run
- when packages are installed or removed.
+ <xref linkend="ch-advanced-packaging"/> covers triggers, another
+ form of script that gets run when packages are installed or
+ removed.
</para>
<para>
Start your scripts with the RPM section marker for the given
@@ -1879,7 +1886,8 @@
Cross Reference
</para>
<para>
- See <xref linkend="ch-using-rpm-db"/> for more on package verification.
+ See <xref linkend="ch-using-rpm-db"/> for more on package
+ verification.
</para>
<para>
The %verify directive names the tests to include or not include.
@@ -2110,8 +2118,8 @@
</para>
<para>
You can also store this setting in a macro file so that it
- applies for all packages you build. See <xref linkend="ch-customizing-rpm"/> for more on
- macro files.
+ applies for all packages you build. See
+ <xref linkend="ch-customizing-rpm"/> for more on macro files.
</para>
<para>
While the Fascist build policy may be an annoyance, it can prove
@@ -2475,7 +2483,7 @@
Cross Reference
</para>
<para>
- <xref linkend="ch-scripting"/> covers shell scripting with RPM.
+ <xref linkend="ch-scripting"/> covers shell scripting with RPM.
</para>
<para>
With parameters, you can expand the normal definition of a macro
Index: rpm-guide-transactions-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-transactions-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-transactions-en.xml 10 Nov 2005 22:30:07 -0000 1.4
+++ rpm-guide-transactions-en.xml 14 Nov 2005 21:55:05 -0000 1.5
@@ -152,7 +152,8 @@
Cross Reference
</para>
<para>
- The gnorpm command is covered in <xref linkend="ch-management-software"/> . The rpmrebuild package
+ The gnorpm command is covered in
+ <xref linkend="ch-management-software"/> . The rpmrebuild package
is covered in the "Saving Old Packages" section in this chapter.
</para>
<para>
@@ -322,7 +323,8 @@
Cross Reference
</para>
<para>
- <xref linkend="ch-using-rpm-db"/> describes the --queryformat option.
+ <xref linkend="ch-using-rpm-db"/> describes the --queryformat
+ option.
</para>
<para>
There is also a transaction ID for removal, the REMOVETID. You
@@ -499,11 +501,11 @@
<para>
Because of all these limitations, rollbacks do not work in all
situations. In place of the --rollback option, you can use the
- query shortcuts introduced in <xref linkend="ch-using-rpm-db"/> and find the packages
- you have installed recently (if that is what you want to roll
- back). In this case, you can use the rpm command to remove the
- packages you want to get rid of and reinstall the packages you
- want to restore.
+ query shortcuts introduced in <xref linkend="ch-using-rpm-db"/>
+ and find the packages you have installed recently (if that is
+ what you want to roll back). In this case, you can use the rpm
+ command to remove the packages you want to get rid of and
+ reinstall the packages you want to restore.
</para>
<para>
In many cases, this manual approach is safest, and you will have
@@ -527,8 +529,9 @@
The package created by the --repackage option is not a complete
RPM package. You can use the rpmbuild command to make it into a
complete package, but by itself, it will not be a complete
- package. See Chapters 10, 11, and 12 for more on building
- packages.
+ package. See <xref linkend="ch-specfiles"/>,
+ <xref linkend="ch-advanced-packaging"/>, and
+ <xref linkend="ch-rpmbuild"/> for more on building packages.
</para>
<para/>
<para>
@@ -547,8 +550,8 @@
Note
</para>
<para>
- The up2date name comes from the &RH; service for keeping a
- system up to date with regard to package versions.
+ The up2date name comes from the &RH; service for keeping a system
+ up to date with regard to package versions.
</para>
<para>
For example, say you have a package, jikes (a Java programming
Index: rpm-guide-using-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-using-rpm-en.xml 10 Nov 2005 22:30:07 -0000 1.4
+++ rpm-guide-using-rpm-en.xml 14 Nov 2005 21:55:05 -0000 1.5
@@ -79,7 +79,9 @@
Cross Reference
</para>
<para>
- Chapters 9 and 12 cover building RPMs from source RPMs.
+ <xref linkend="ch-creating-rpms"/> and
+ <xref linkend="ch-rpmbuild"/> cover building RPMs from source
+ RPMs.
</para>
<para>
The rpm command provides three main operations for upgrading and
@@ -111,8 +113,8 @@
<para/>
<para>
Almost all installation steps use the rpm command with the ���U
- option, short for upgrade, as introduced in <xref linkend="ch-rpm-overview"/> . The basic
- syntax is:
+ option, short for upgrade, as introduced in
+ <xref linkend="ch-rpm-overview"/> . The basic syntax is:
</para>
<para>
rpm -U package_name
@@ -144,9 +146,9 @@
</para>
<para>
This warning comes from the fact that the package was signed,
- but the key was not found. <xref linkend="ch-rpmbuild"/> covers signing packages.
- In most cases, warnings such as this one are not that serious.
- Errors, though, should be treated seriously.
+ but the key was not found. <xref linkend="ch-rpmbuild"/> covers
+ signing packages. In most cases, warnings such as this one are
+ not that serious. Errors, though, should be treated seriously.
</para>
<para>
Note
@@ -971,12 +973,11 @@
</para>
<para>
Note that when you purchase an upgraded version of Linux, such
- as &RHL;, all the packages with the product should be
- properly aligned with each other as to versions. This
- alignment problem is an issue that the Linux vendors, such as
- &RH;, need to take care of. The main problems occur when
- you need packages beyond those offered with your Linux
- distribution.
+ as &RHL;, all the packages with the product should be properly
+ aligned with each other as to versions. This alignment problem
+ is an issue that the Linux vendors, such as &RH;, need to take
+ care of. The main problems occur when you need packages beyond
+ those offered with your Linux distribution.
</para>
<para>
To combine some of these options, you can use --force, which
@@ -1037,11 +1038,11 @@
</para>
<para>
The --aid option depends on a separate package that contains
- an RPM database with all packages installed. For &RH;
- Linux, this package is rpmdb-redhat. This separate database,
- built as if all packages were installed (all packages that
- come with &RHL; in this case), allows the rpm command
- to search for which packages would solve dependencies.
+ an RPM database with all packages installed. For &RH; Linux,
+ this package is rpmdb-redhat. This separate database, built as
+ if all packages were installed (all packages that come with
+ &RHL; in this case), allows the rpm command to search for
+ which packages would solve dependencies.
</para>
</sect3>
<sect3>
@@ -1174,8 +1175,8 @@
</para>
<para>
In addition to pre- and post-installation scripts, the RPM
- system supports triggers, a topic covered in detail in Chapter
- 11.
+ system supports triggers, a topic covered in detail in
+ <xref linkend="ch-advanced-packaging"/>.
</para>
<para>
During installation, you can tell the rpm command not to
@@ -1454,8 +1455,8 @@
configuration file on disk. This is where the rpm command
starts working with some upgrade rules. Note that this special
processing only applies to files marked as configuration files
- within the RPM. <xref linkend="ch-specfiles"/> covers how to mark files as
- configuration files.
+ within the RPM. <xref linkend="ch-specfiles"/> covers how to
+ mark files as configuration files.
</para>
<para>
If the file on disk is identical to the file in the original
@@ -1689,9 +1690,9 @@
example, rarely come with source code. In this case, obviously,
no source RPMs are available. Or, a source RPM for a commercial
application may provide no source code, but still provide a way
- to build the resulting application. See <xref linkend="ch-specfiles"/> for more on
- the source files and options for not including the sources in a
- source RPM.
+ to build the resulting application. See
+ <xref linkend="ch-specfiles"/> for more on the source files and
+ options for not including the sources in a source RPM.
</para>
<para>
Open-source Software
@@ -1992,7 +1993,8 @@
Cross Reference
</para>
<para>
- See <xref linkend="ch-customizing-rpm"/> for more on the --showrc option.
+ See <xref linkend="ch-customizing-rpm"/> for more on the --showrc
+ option.
</para>
<para>
The --version option tells the rpm command to print out the
18 years, 5 months
mirror-tutorial mirror-tutorial-en.xml,1.16,1.17
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22945
Modified Files:
mirror-tutorial-en.xml
Log Message:
Additional createrepo info (#172819)
Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- mirror-tutorial-en.xml 11 Nov 2005 15:33:22 -0000 1.16
+++ mirror-tutorial-en.xml 11 Nov 2005 16:58:48 -0000 1.17
@@ -199,7 +199,7 @@
<revdescription>
<para>
Added some additional information about repository
- configuration (#172815).
+ configuration (#172815, #172819).
</para>
</revdescription>
</revision>
@@ -1314,6 +1314,22 @@
</screen>
<para>
+ To create repository data for package groups in addition to
+ the package files, use the <command>createrepo -g</command>
+ command. The <option>-g</option> option requires a parameter
+ which points to the group file, <emphasis>relative</emphasis>
+ to the given location of the package data. The following
+ command creates the package group data corresponding to the
+ repository directly above. Note the relative location of the
+ group file
+ <filename>/var/www/mirror/fedora/linux/core/&FCVER;i386/os/Fedora/base/comps.xml</filename>.
+ </para>
+
+<screen>
+<userinput>createrepo -g Fedora/base/comps.xml /var/www/mirror/fedora/linux/core/&FCVER;/i386/os</userinput>
+</screen>
+
+ <para>
You may have certain clients who update their version of
<command>yum</command> in a non-prescribed way. To minimize
problems for your clients, create both kinds of repository
18 years, 5 months
mirror-tutorial mirror-tutorial-en.xml,1.15,1.16
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20424
Modified Files:
mirror-tutorial-en.xml
Log Message:
Update information on repo files (#172815)
Index: mirror-tutorial-en.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/mirror-tutorial-en.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- mirror-tutorial-en.xml 9 Nov 2005 23:41:58 -0000 1.15
+++ mirror-tutorial-en.xml 11 Nov 2005 15:33:22 -0000 1.16
@@ -6,8 +6,8 @@
%FEDORA-ENTITIES-EN;
<!ENTITY BOOKNAME "mirror-tutorial">
-<!ENTITY BOOKVERSION "0.35">
-<!ENTITY BOOKDATE "2005-11-09">
+<!ENTITY BOOKVERSION "0.36">
+<!ENTITY BOOKDATE "2005-11-11">
<!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)"> <!-- change version of manual and date here -->
<!ENTITY BUG-NUM "130125">
@@ -192,6 +192,17 @@
</para>
</revdescription>
</revision>
+ <revision>
+ <revnumber>0.36</revnumber>
+ <date>2005-11-11</date>
+ <authorinitials>PaulWFrields</authorinitials>
+ <revdescription>
+ <para>
+ Added some additional information about repository
+ configuration (#172815).
+ </para>
+ </revdescription>
+ </revision>
</revhistory>
</articleinfo>
@@ -804,7 +815,7 @@
<para>
If you are not exceedingly careful in using these switches, it is
possible to delete large portions of your mirrored data. Fixing this
- problem might simply require performing the copying steps outlined
+ problem might require performing the copying steps outlined
in <xref linkend="sn-copying-original-distribution"/> above. On the
other hand, if you are also careless about your destination path,
and you are running as root, you could put your entire system at
@@ -1192,7 +1203,7 @@
server. It can do this via HTTP or FTP, as well as using
standard file system calls (either local or remote via NFS). The
client computes solutions to any package dependencies using the
- downloaded header information, and simply requests all necessary
+ downloaded header information, and requests all necessary
RPM packages once it has finished. The <command>yum</command>
command relies on <command>rpm</command> functions to perform
many of the computations involved in the process.
@@ -1361,10 +1372,10 @@
<example>
<title>Example
- <filename>/etc/yum.repos.d/fedora.repo</filename></title>
+ <filename>/etc/yum.repos.d/fedora-mirror.repo</filename></title>
<screen>
-<computeroutput>[base]
+<computeroutput>[mirror]
name=Fedora Core $releasever - $basearch - Base
baseurl=http://server.mydomain.net/mirror/fedora/linux/core/$releasever/$...
enabled=1
@@ -1382,9 +1393,22 @@
</para>
<para>
- For more information about these configuration files, refer to the
- "Software Management with <command>yum</command>" tutorial online
- at <ulink url="http://fedora.redhat.com/docs/yum/"/>.
+ If you want clients to use your mirror in place of the official
+ repositories, disable the existing repositories. To do this, edit
+ the client's file for the official repository to include the
+ directive <userinput>enabled=0</userinput>. You will need
+ <systemitem class="username">root</systemitem> access to edit
+ these files.
+ </para>
+
+ <para>
+ Many repositories provide their own installable RPM packages
+ containing these configuration files. When a user installs the
+ RPM, the new files in <filename>/etc/yum.repos.d/</filename>
+ reference that repository. These packages simplify the addition
+ of new repositories for end users. Whether you use such a package
+ yourself will depend on the number and skill set of clients your
+ repository serves.
</para>
</section>
18 years, 5 months
rpm-guide rpm-guide-advanced-packaging-en.xml, 1.3, 1.4 rpm-guide-creating-rpms-en.xml, 1.3, 1.4 rpm-guide-customizing-rpm-en.xml, 1.2, 1.3 rpm-guide-dependencies-en.xml, 1.2, 1.3 rpm-guide-extra-packaging-tools-en.xml, 1.3, 1.4 rpm-guide-management-software-en.xml, 1.3, 1.4 rpm-guide-online-resources-en.xml, 1.3, 1.4 rpm-guide-other-linuxes-en.xml, 1.3, 1.4 rpm-guide-other-os-en.xml, 1.3, 1.4 rpm-guide-packaging-guidelines-en.xml, 1.3, 1.4 rpm-guide-programming-c-en.xml, 1.3, 1.4 rpm-guide-programming-perl
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22002
Modified Files:
rpm-guide-advanced-packaging-en.xml
rpm-guide-creating-rpms-en.xml
rpm-guide-customizing-rpm-en.xml rpm-guide-dependencies-en.xml
rpm-guide-extra-packaging-tools-en.xml
rpm-guide-management-software-en.xml
rpm-guide-online-resources-en.xml
rpm-guide-other-linuxes-en.xml rpm-guide-other-os-en.xml
rpm-guide-packaging-guidelines-en.xml
rpm-guide-programming-c-en.xml
rpm-guide-programming-perl-en.xml
rpm-guide-programming-python-en.xml rpm-guide-rpmbuild-en.xml
rpm-guide-scripting-en.xml rpm-guide-specfile-syntax-en.xml
rpm-guide-specfiles-en.xml rpm-guide-transactions-en.xml
rpm-guide-using-rpm-db-en.xml rpm-guide-using-rpm-en.xml
Log Message:
Bulk replaced "Chapter X" and "Appendix Y" references with links
Index: rpm-guide-advanced-packaging-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-advanced-packaging-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-advanced-packaging-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-advanced-packaging-en.xml 10 Nov 2005 22:30:06 -0000 1.4
@@ -75,7 +75,7 @@
Cross Reference
</para>
<para>
- Chapter 6 covers more on dependencies. The Obsoletes dependencies
+ <xref linkend="ch-dependencies"/> covers more on dependencies. The Obsoletes dependencies
are usually only used when a package is renamed, such as the
apache package becoming the httpd package, starting in &RH;
Linux 8.0. The httpd package obsoletes the apache package.
@@ -345,7 +345,7 @@
Cross Reference
</para>
<para>
- Chapter 14 covers a common problem of handling circular
+ <xref linkend="ch-packaging-guidelines"/> covers a common problem of handling circular
dependencies using prerequisites.
</para>
</sect2>
@@ -408,7 +408,7 @@
Cross Reference
</para>
<para>
- Chapter 14 covers how to turn off the automatic generation of
+ <xref linkend="ch-packaging-guidelines"/> covers how to turn off the automatic generation of
dependencies.
</para>
</sect2>
@@ -532,7 +532,7 @@
removed.
</para>
<para>
- The anonftp package, mentioned in Chapter 6, has a lot of
+ The anonftp package, mentioned in <xref linkend="ch-dependencies"/> , has a lot of
triggers. Many of these set up a number of commands to be locally
available to the anonftp package. This networking package is also
closely tied to the version of the C library, glibc, as shown in
@@ -866,7 +866,7 @@
</para>
<para>
*Control the tests used to verify each file, as described in
- Chapter 10
+ <xref linkend="ch-specfiles"/>
</para>
<para>
*Create a verify script that performs other tests
@@ -898,7 +898,7 @@
Cross Reference
</para>
<para>
- See Chapter 5 for more on package verification.
+ See <xref linkend="ch-using-rpm-db"/> for more on package verification.
</para>
</sect1>
<sect1>
@@ -1187,7 +1187,7 @@
Cross Reference
</para>
<para>
- Chapter 10 covers the %setup macro and lists the available
+ <xref linkend="ch-specfiles"/> covers the %setup macro and lists the available
options.
</para>
</sect2>
@@ -1207,7 +1207,7 @@
Cross Reference
</para>
<para>
- Chapter 19 covers using RPM on other versions of Linux.
+ <xref linkend="ch-other-linuxes"/> covers using RPM on other versions of Linux.
</para>
<para>
With a relocatable package, though, you allow the user to redefine
@@ -1295,7 +1295,7 @@
Cross Reference
</para>
<para>
- Chapter 4 covers how to install or upgrade packages into
+ <xref linkend="ch-using-rpm"/> covers how to install or upgrade packages into
different directories using the --relocate and --prefix options.
</para>
</sect2>
@@ -1356,7 +1356,7 @@
Cross Reference
</para>
<para>
- See Chapter 21 for more on macro file locations, and Chapters 19
+ See <xref linkend="ch-customizing-rpm"/> for more on macro file locations, and Chapters 19
and 20 for more on using RPM on other versions of Linux and other
operating systems, respectively.
</para>
@@ -1417,7 +1417,7 @@
</para>
<para>
Many of the macros you will test this way are set up with the
- --with command-line parameter. See Chapter 19 for details.
+ --with command-line parameter. See <xref linkend="ch-other-linuxes"/> for details.
</para>
</sect2>
<sect2>
@@ -1537,7 +1537,7 @@
Cross Reference
</para>
<para>
- Chapter 21 covers RPM architecture and operating system names.
+ <xref linkend="ch-customizing-rpm"/> covers RPM architecture and operating system names.
</para>
<para>
You can pass more than one architecture name, separated by
Index: rpm-guide-creating-rpms-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-creating-rpms-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-creating-rpms-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-creating-rpms-en.xml 10 Nov 2005 22:30:06 -0000 1.4
@@ -196,7 +196,7 @@
number of bundles.
</para>
<para>
- As covered in Chapter 2, a major tenet of the philosophy behind
+ As covered in <xref linkend="ch-intro-rpm"/> , a major tenet of the philosophy behind
RPM is to start with pristine���unmodified--sources. You may
need to patch or customize the sources for your environment, but
you can always go back to the original sources.
@@ -791,7 +791,7 @@
Cross Reference
</para>
<para>
- See Chapter 21 for more on the use of the rpmrc settings.
+ See <xref linkend="ch-customizing-rpm"/> for more on the use of the rpmrc settings.
</para>
<para>
For now, it is easiest to just change to the /usr/src/redhat
@@ -1544,7 +1544,7 @@
Cross Reference
</para>
<para>
- Chapter 12 covers a number of addition options for the rpmbuild
+ <xref linkend="ch-rpmbuild"/> covers a number of addition options for the rpmbuild
command that you can use to customize the build.
</para>
</sect2>
@@ -1636,7 +1636,7 @@
Cross Reference
</para>
<para>
- See the on "Verifying Installed RPM Packages" section in Chapter 5
+ See the on "Verifying Installed RPM Packages" section in <xref linkend="ch-using-rpm-db"/>
for more on the -V option.
</para>
</sect1>
Index: rpm-guide-customizing-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-customizing-rpm-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-customizing-rpm-en.xml 26 Oct 2005 01:54:11 -0000 1.2
+++ rpm-guide-customizing-rpm-en.xml 10 Nov 2005 22:30:06 -0000 1.3
@@ -61,7 +61,7 @@
</para>
<para>
The macro syntax is used in the query formats introduced in
- Chapter 5.
+ <xref linkend="ch-using-rpm-db"/> .
</para>
<sect2>
<title>Defining macros</title>
@@ -176,7 +176,7 @@
Cross Reference
</para>
<para>
- Chapter 10 covers spec files.
+ <xref linkend="ch-specfiles"/> covers spec files.
</para>
<para>
In addition to these options, you can use a syntax of %{-a} to
@@ -746,7 +746,7 @@
Cross Reference
</para>
<para>
- Chapter 5 covers the query format.
+ <xref linkend="ch-using-rpm-db"/> covers the query format.
</para>
<para>
For example, the following entry defines the --requires and ���R
@@ -792,7 +792,7 @@
</para>
<para>
The command_name must be the name passed to the C poptGetContext
- function, covered in Chapter 16.
+ function, covered in <xref linkend="ch-programming-c"/> .
</para>
<para>
Follow this with alias and then the option. You will need
@@ -882,7 +882,7 @@
Cross Reference
</para>
<para>
- Chapter 16 shows how to program with the popt library.
+ <xref linkend="ch-programming-c"/> shows how to program with the popt library.
</para>
</sect2>
<sect2>
Index: rpm-guide-dependencies-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-dependencies-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-dependencies-en.xml 26 Oct 2005 01:54:11 -0000 1.2
+++ rpm-guide-dependencies-en.xml 10 Nov 2005 22:30:06 -0000 1.3
@@ -97,7 +97,7 @@
<para>
Package dependencies and capabilities are very important when
creating spec files for building your own RPM packages, the
- subject of Chapter 10.
+ subject of <xref linkend="ch-specfiles"/> .
</para>
<para>
When you install a package, the capability information is stored
@@ -147,7 +147,7 @@
Cross Reference
</para>
<para>
- Chapter 4 covers ways to force the rpm command to do what you
+ <xref linkend="ch-using-rpm"/> covers ways to force the rpm command to do what you
want, although this can cause problems if you try to force the
issue and remove a crucial package. In virtually all cases, do
not use any of the force options, as this can cause problems
@@ -235,7 +235,7 @@
<para>
The RPM system will prevent you from installing packages that
conflict with other packages. You can force the issue, using the
- techniques described in Chapter 4, and override the RPM system.
+ techniques described in <xref linkend="ch-using-rpm"/> , and override the RPM system.
But in most cases, you should not install packages that
conflict.
</para>
@@ -305,7 +305,7 @@
</para>
<para>
There are quite a few more options you can use with the rpm ���q
- command for querying packages. See Chapter 5 for more on querying
+ command for querying packages. See <xref linkend="ch-using-rpm-db"/> for more on querying
packages and package files.
</para>
<sect2>
@@ -465,7 +465,7 @@
Always check what a package requires before installing the
package. You can also use the --test option when trying to
install the package to first test whether the installation can
- proceed. See Chapter 4 for details on installing packages and
+ proceed. See <xref linkend="ch-using-rpm"/> for details on installing packages and
the --test option. The rpm command will perform all these checks
for you anyway. Checking in advance, though, with the --test
option, helps avoid dependency hell with circular dependencies.
@@ -751,7 +751,7 @@
won���t work with another.
</para>
<para>
- The force options discussed in Chapter 4 allow you to override
+ The force options discussed in <xref linkend="ch-using-rpm"/> allow you to override
conflicts, if absolutely necessary. In most cases, though, a
conflict presents you with the choice to install one or the
other of the packages, but not both.
Index: rpm-guide-extra-packaging-tools-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-extra-packaging-tools-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-extra-packaging-tools-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-extra-packaging-tools-en.xml 10 Nov 2005 22:30:06 -0000 1.4
@@ -346,7 +346,7 @@
Cross Reference
</para>
<para>
- See Appendix G for more on the GNU GPL, or General Public
+ See <xref linkend="ch-licensing"/> for more on the GNU GPL, or General Public
License.
</para>
<para>
@@ -870,7 +870,7 @@
RUST appears to have stopped, so extension of RUST to become a
more generally useful IDE for RPM generation is not likely to
happen. However, the project is licensed under the GNU GPL
- (Appendix G), so it might be resumed by another developer or
+ (<xref linkend="ch-licensing"/> ), so it might be resumed by another developer or
team of developers.
</para>
</sect2>
@@ -915,7 +915,7 @@
</para>
<para>
For more discussion of the future of RPM, you can turn to
- Chapter 22.
+ <xref linkend="ch-rpm-evolution"/> .
</para>
</sect2>
<sect2>
@@ -953,7 +953,7 @@
</para>
<para>
RPM ships with an rpm2cpio utility that can be used to convert
- RPM package files to cpio files. (Chapter 3 introduces the
+ RPM package files to cpio files. (<xref linkend="ch-rpm-overview"/> introduces the
rpm2cpio utility.) For example, if you have a source RPM package
file and want to extract its files without having to install it,
you can process it through rpm2cpio. The rpm2cpio command takes
Index: rpm-guide-management-software-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-management-software-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-management-software-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-management-software-en.xml 10 Nov 2005 22:30:06 -0000 1.4
@@ -441,7 +441,7 @@
<para>
With rpm2html, each package is displayed as a single HTML page
that describes the package using information much like that
- returned by the rpm -qi command, covered in Chapter 4. The HTML
+ returned by the rpm -qi command, covered in <xref linkend="ch-using-rpm"/> . The HTML
page also lists the capabilities the package requires and those
it provides. This shows the needed dependency information.
Finally, the page includes a download link to download the RPM
@@ -551,7 +551,7 @@
Cross Reference
</para>
<para>
- See Chapter 10 for more on RPM spec files.
+ See <xref linkend="ch-specfiles"/> for more on RPM spec files.
</para>
</sect3>
<sect3>
Index: rpm-guide-online-resources-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-online-resources-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-online-resources-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-online-resources-en.xml 10 Nov 2005 22:30:06 -0000 1.4
@@ -354,10 +354,10 @@
Cross Reference
</para>
<para>
- Appendix F lists links for a number of text editors.
+ <xref linkend="ch-development-tools"/> lists links for a number of text editors.
</para>
<para>
- *The rpmlint tool mentioned in Chapter 13 is available at
+ *The rpmlint tool mentioned in <xref linkend="ch-extra-packaging-tools"/> is available at
http://people.mandrakesoft.com/~flepied/projects/rpmlint/.
</para>
<para>
@@ -561,7 +561,7 @@
Cross Reference
</para>
<para>
- Appendix F lists links for a number of Integrated Development
+ <xref linkend="ch-development-tools"/> lists links for a number of Integrated Development
Environments, or IDEs, aimed at programmers.
</para>
</sect2>
Index: rpm-guide-other-linuxes-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-other-linuxes-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-other-linuxes-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-other-linuxes-en.xml 10 Nov 2005 22:30:06 -0000 1.4
@@ -140,7 +140,7 @@
The only real solution to this problem is to turn off dependency
checks on installing, with the --nodeps option. Then you must
check manually that your system really does provide all the
- necessary dependencies. Use the techniques shown in Chapter 6 to
+ necessary dependencies. Use the techniques shown in <xref linkend="ch-dependencies"/> to
verify all the dependencies are met on your system.
</para>
<para>
@@ -200,7 +200,7 @@
<para>
You can use the rpm -qf command to query which package owns a
given file. You can use the rpm -q --whatprovides command to
- query for which package provides a given capability. Chapter 6
+ query for which package provides a given capability. <xref linkend="ch-dependencies"/>
covers more on dependencies.
</para>
<para>
@@ -263,7 +263,7 @@
Cross Reference
</para>
<para>
- Chapter 4 covers the --badreloc option.
+ <xref linkend="ch-using-rpm"/> covers the --badreloc option.
</para>
<para>
But, while the --badreloc option will relocate the files in a
@@ -457,7 +457,7 @@
As much as possible, depend on your own RPM macros. You can
define your macros in terms of vendor-specific macros using
conditional statements in your spec files, a topic covered in
- Chapter 11. You can also read examples in the ���Build
+ <xref linkend="ch-advanced-packaging"/> . You can also read examples in the ���Build
Environment and Macros��� section of this chapter.
</para>
<para>
@@ -478,7 +478,7 @@
Cross Reference
</para>
<para>
- Chapter 10 covers the spec file format. Chapter 11 covers making
+ <xref linkend="ch-specfiles"/> covers the spec file format. <xref linkend="ch-advanced-packaging"/> covers making
relocatable packages.
</para>
<para>
@@ -580,7 +580,7 @@
Cross Reference
</para>
<para>
- Chapter 21 covers RPM macros.
+ <xref linkend="ch-customizing-rpm"/> covers RPM macros.
</para>
<para>
The macros that specifically help you with platform
Index: rpm-guide-other-os-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-other-os-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-other-os-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-other-os-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -115,7 +115,7 @@
Cross Reference
</para>
<para>
- See Chapter 2 for more on the philosophy behind RPM.
+ See <xref linkend="ch-intro-rpm"/> for more on the philosophy behind RPM.
</para>
<para>
If you decide to use RPM on a non-Linux system, the first step is
@@ -945,7 +945,7 @@
Cross Reference
</para>
<para>
- Chapter 21 covers RPM customization.
+ <xref linkend="ch-customizing-rpm"/> covers RPM customization.
</para>
<para>
Initializing the RPM database creates the necessary structure
@@ -1038,7 +1038,7 @@
<para>
You need to provide a spec file header to make a complete spec
file. This header should contain the Summary, Name, Version,
- and Release settings, at least. Chapter 10 covers these spec
+ and Release settings, at least. <xref linkend="ch-specfiles"/> covers these spec
file tags.
</para>
<para>
@@ -1234,7 +1234,7 @@
Cross Reference
</para>
<para>
- Chapter 9 covers how to run the rpmbuild command, and Chapter
+ <xref linkend="ch-creating-rpms"/> covers how to run the rpmbuild command, and Chapter
10 covers spec files in detail.
</para>
</sect3>
@@ -1342,7 +1342,7 @@
Cross Reference
</para>
<para>
- Chapter 21 covers how to customize the RPM settings and macros,
+ <xref linkend="ch-customizing-rpm"/> covers how to customize the RPM settings and macros,
along with the popt aliases.
</para>
<para>
@@ -1406,7 +1406,7 @@
Cross Reference
</para>
<para>
- See Chapter 21 for more on how to customize the rc and macro
+ See <xref linkend="ch-customizing-rpm"/> for more on how to customize the rc and macro
settings.
</para>
<para>
@@ -1420,8 +1420,8 @@
Cross Reference
</para>
<para>
- See Chapter 19 for more information on setting up a build
- environment for RPMs. Chapter 19 focuses on other Linux systems,
+ See <xref linkend="ch-other-linuxes"/> for more information on setting up a build
+ environment for RPMs. <xref linkend="ch-other-linuxes"/> focuses on other Linux systems,
but many of the same techniques apply.
</para>
<para>
@@ -1522,7 +1522,7 @@
Cross Reference
</para>
<para>
- See Chapter 12 for more on using the --target option to the
+ See <xref linkend="ch-rpmbuild"/> for more on using the --target option to the
rpmbuild command.
</para>
<para>
@@ -1542,7 +1542,7 @@
Cross Reference
</para>
<para>
- See Chapter 19 for information on how to turn off the automatic
+ See <xref linkend="ch-other-linuxes"/> for information on how to turn off the automatic
generation of dependencies.
</para>
<para>
Index: rpm-guide-packaging-guidelines-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-packaging-guidelines-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-packaging-guidelines-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-packaging-guidelines-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -238,7 +238,7 @@
</para>
<para>
If you do need a directory installed as part of your package,
- use the %dir directive, described in Chapter 10.
+ use the %dir directive, described in <xref linkend="ch-specfiles"/> .
</para>
</sect2>
<sect2>
@@ -254,7 +254,7 @@
Cross Reference
</para>
<para>
- Chapter 4 covers how to install or upgrade packages while
+ <xref linkend="ch-using-rpm"/> covers how to install or upgrade packages while
ignoring dependency checks. In general, you do not want to
ignore these checks.
</para>
@@ -343,7 +343,7 @@
Cross Reference
</para>
<para>
- Chapter 10 covers the spec file.
+ <xref linkend="ch-specfiles"/> covers the spec file.
</para>
<para>
Keeping your patches separate from the original sources makes
@@ -370,7 +370,7 @@
Cross Reference
</para>
<para>
- Chapter 17 covers Python programming.
+ <xref linkend="ch-rpm-programming-python"/> covers Python programming.
</para>
<para>
This last division is important. The Python RPM draws in as a
@@ -481,7 +481,7 @@
Cross Reference
</para>
<para>
- Chapter 13 covers RPM-building tools. Appendix F covers the
+ <xref linkend="ch-extra-packaging-tools"/> covers RPM-building tools. <xref linkend="ch-development-tools"/> covers the
Eclipse Integrated Development Environment.
</para>
<para>
@@ -562,7 +562,7 @@
Cross Reference
</para>
<para>
- Chapter 12 covers signing packages.
+ <xref linkend="ch-rpmbuild"/> covers signing packages.
</para>
</sect3>
<sect3>
Index: rpm-guide-programming-c-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-c-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-programming-c-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-programming-c-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -115,7 +115,7 @@
Cross Reference
</para>
<para>
- See Chapter 8 for more on the &RH; package management tool.
+ See <xref linkend="ch-management-software"/> for more on the &RH; package management tool.
</para>
<para>
The gcc package requires a number of capabilities. Make sure you
@@ -131,7 +131,7 @@
Cross Reference
</para>
<para>
- Appendix F covers Linux text editors and development tools.
+ <xref linkend="ch-development-tools"/> covers Linux text editors and development tools.
</para>
<para>
Once you have a C programming environment set up, you next need
@@ -185,7 +185,7 @@
Cross Reference
</para>
<para>
- Chapter 17 covers programming RPM with Python.
+ <xref linkend="ch-rpm-programming-python"/> covers programming RPM with Python.
</para>
<para>
In addition to rpmlib.h, the header file rpmcli.h defines a
@@ -346,7 +346,7 @@
</para>
<para>
You can use the rpm command and the queries introduced in
- Chapter 5 to determine exactly where the header files are
+ <xref linkend="ch-using-rpm-db"/> to determine exactly where the header files are
located. Simply execute the following command:
</para>
<para>
@@ -531,7 +531,7 @@
Cross Reference
</para>
<para>
- Chapter 21 covers customizing RPM.
+ <xref linkend="ch-customizing-rpm"/> covers customizing RPM.
</para>
<para>
Your C programs need to access these RPM system settings to
@@ -832,7 +832,7 @@
Cross Reference
</para>
<para>
- Chapter 21 covers macros in depth. In your C programs, your
+ <xref linkend="ch-customizing-rpm"/> covers macros in depth. In your C programs, your
code will likely need to expand the value of macros to place
data in the proper directories, determine the platform
architecture, and so on.
@@ -1013,13 +1013,13 @@
</para>
<para>
This example defines rpm --requires as really a query using the
- --qf or --queryformat options covered in Chapter 5.
+ --qf or --queryformat options covered in <xref linkend="ch-using-rpm-db"/> .
</para>
<para>
Cross Reference
</para>
<para>
- See Chapter 21 for more on defining popt aliases.
+ See <xref linkend="ch-customizing-rpm"/> for more on defining popt aliases.
</para>
</sect2>
<sect2>
@@ -2268,7 +2268,7 @@
Cross Reference
</para>
<para>
- Chapter 17 covers the Python RPM API.
+ <xref linkend="ch-rpm-programming-python"/> covers the Python RPM API.
</para>
<sect2>
<title>Opening RPM files</title>
@@ -2308,7 +2308,7 @@
Cross Reference
</para>
<para>
- Chapter 3 introduces the lead and signature.
+ <xref linkend="ch-rpm-overview"/> introduces the lead and signature.
</para>
<para>
Even if your programs don���t want to examine the lead or
@@ -2555,7 +2555,7 @@
<para>
When you call headerGetEntry, you must identify the tag you want
from the header. This tag is an identifier for the --queryformat
- tags introduced in Chapter 5. The file rpmlib.h lists the
+ tags introduced in <xref linkend="ch-using-rpm-db"/> . The file rpmlib.h lists the
various tags, such as RPMTAG_NAME, RPMTAG_VERSION, and
RPMTAG_RELEASE.
</para>
Index: rpm-guide-programming-perl-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-perl-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-programming-perl-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-programming-perl-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -74,7 +74,7 @@
Cross Reference
</para>
<para>
- Many of the RPM tools covered in Chapter 8 are written in Perl.
+ Many of the RPM tools covered in <xref linkend="ch-management-software"/> are written in Perl.
</para>
<sect1>
<title>Getting and Using the Perl RPM Modules</title>
@@ -160,7 +160,7 @@
</para>
<para>
These are the same tags introduced with the --queryformat option
- to the rpm command discussed in Chapter 5.
+ to the rpm command discussed in <xref linkend="ch-using-rpm-db"/> .
</para>
<para>
The tag subroutine returns the value of a given tag. For
@@ -1167,7 +1167,7 @@
Cross Reference
</para>
<para>
- Chapter 5 covers more on these tags.
+ <xref linkend="ch-using-rpm-db"/> covers more on these tags.
</para>
</sect3>
<sect3>
@@ -1526,7 +1526,7 @@
packages that are older than the designated master system.
RPM::Make, also part of the RPM-Tools bundle, helps create RPM
packages from a Perl script. This module does not support all the
- spec file options described in Chapter 10, but it can help you
+ spec file options described in <xref linkend="ch-specfiles"/> , but it can help you
make simple packages.
</para>
<para>
Index: rpm-guide-programming-python-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-programming-python-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-guide-programming-python-en.xml 31 Oct 2005 23:18:20 -0000 1.4
+++ rpm-guide-programming-python-en.xml 10 Nov 2005 22:30:07 -0000 1.5
@@ -45,7 +45,7 @@
Cross Reference
</para>
<para>
- Appendix H covers Linux text editors and development tools.
+ <xref linkend="ch-development-tools"/> covers Linux text editors and development tools.
</para>
<para>
If you want to make a graphical user interface in your Python
@@ -67,7 +67,7 @@
Cross Reference
</para>
<para>
- Chapter 4 covers installing packages.
+ <xref linkend="ch-using-rpm"/> covers installing packages.
</para>
</sect2>
<sect2>
@@ -250,7 +250,7 @@
<sect1>
<title>Programming with the RPM Database</title>
<para>
- Compared to the RPM C API, discussed in Chapter 16, the Python API
+ Compared to the RPM C API, discussed in <xref linkend="ch-programming-c"/> , the Python API
is much simpler and requires many fewer programming statements to
get your job done.
</para>
@@ -388,7 +388,7 @@
Cross Reference
</para>
<para>
- See Chapter 5 for more on initializing, rebuilding, and
+ See <xref linkend="ch-using-rpm-db"/> for more on initializing, rebuilding, and
verifying RPM databases.
</para>
<para>
@@ -701,7 +701,7 @@
Cross Reference
</para>
<para>
- Chapter 5 covers query formats.
+ <xref linkend="ch-using-rpm-db"/> covers query formats.
</para>
<para>
The basic syntax is as follows:
@@ -1187,7 +1187,7 @@
For more on these patterns, see the online manual pages for
fnmatch(3), glob(7), regcomp(3), regex(7), and strcmp(3). The
pattern method calls rpmdbSetIteratorRE from the C API, covered
- in the ���Database Iterators��� section in Chapter 16.
+ in the ���Database Iterators��� section in <xref linkend="ch-programming-c"/> .
</para>
<para>
To query for all packages starting with py, for example, you can
@@ -1620,7 +1620,7 @@
<sect1>
<title>Dependency Comparisons</title>
<para>
- Dependency sets, first introduced in Chapter 16 on C programming,
+ Dependency sets, first introduced in <xref linkend="ch-programming-c"/> on C programming,
allow you to compare the dependencies between two packages. One of
the most common uses for this is to compare a package file against
a version on disk to see if the package file holds a newer version
@@ -1739,7 +1739,7 @@
</para>
<para>
The Python script in Listing 17-5 is essentially the same as the
- longer C program vercompare.c in Listing 16-4 in Chapter 16.
+ longer C program vercompare.c in Listing 16-4 in <xref linkend="ch-programming-c"/> .
</para>
<para>
This script takes in a package file name on the command line,
@@ -3044,7 +3044,7 @@
This chapter introduces the high-level RPM API for Python
programming. You can use this API from Python scripts to perform
RPM functionality, just as you can write C programs using the RPM
- C API covered in Chapter 16.
+ C API covered in <xref linkend="ch-programming-c"/> .
</para>
<para>
In general, the Python API is simpler and requires fewer code
Index: rpm-guide-rpmbuild-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-rpmbuild-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-rpmbuild-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-rpmbuild-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -66,7 +66,7 @@
Note
</para>
<para>
- As mentioned in Chapter 9, previous versions of the RPM system
+ As mentioned in <xref linkend="ch-creating-rpms"/> , previous versions of the RPM system
used the rpm command with a -b, for build, option. This option is
no longer supported. Use the rpmbuild command to build RPMs.
</para>
@@ -369,7 +369,7 @@
</para>
<para>
The --target option sets the target architecture at build time.
- Chapter 4 covers how you can use the --ignoreos and --ignorearch
+ <xref linkend="ch-using-rpm"/> covers how you can use the --ignoreos and --ignorearch
options when installing RPMs to ignore the operating system and
architecture that is flagged within the RPM. Of course, this
works only if you are installing on a compatible architecture.
@@ -551,7 +551,7 @@
rpmbuild -tBuildStage compressed_tar_archive
</para>
<para>
- The -t option is a lot like the -b option covered in Chapter 9,
+ The -t option is a lot like the -b option covered in <xref linkend="ch-creating-rpms"/> ,
except -t tells rpmbuild to build an RPM from a compressed tar
archive instead of from an RPM spec file. You still need a spec
file. These commands just assume that the spec file is located
@@ -724,7 +724,7 @@
Cross Reference
</para>
<para>
- Chapter 10 covers the spec file in depth.
+ <xref linkend="ch-specfiles"/> covers the spec file in depth.
</para>
<para>
Because they are RPMs themselves, source RPMs act like other RPMs.
@@ -752,7 +752,7 @@
<para>
Once installation is complete, you can use the rpmbuild command to
create a binary RPM from the sources in the source RPM, using the
- -b command-line options introduced in Chapter 9. The next sections
+ -b command-line options introduced in <xref linkend="ch-creating-rpms"/> . The next sections
show more shortcuts with source RPMs.
</para>
<sect2>
@@ -1361,7 +1361,7 @@
Cross Reference
</para>
<para>
- Chapter 21 covers RPM macros and the $HOME/.rpmmacros file.
+ <xref linkend="ch-customizing-rpm"/> covers RPM macros and the $HOME/.rpmmacros file.
</para>
<para>
Inside the file, change the %gpg_path macro to the .gnupg
Index: rpm-guide-scripting-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-scripting-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-scripting-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-scripting-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -224,9 +224,9 @@
Cross Reference
</para>
<para>
- This chapter covers shell scripting. Chapter 16 covers C
- programming. Chapter 17 covers Python scripting and programming,
- and Chapter 18 covers Perl scripting.
+ This chapter covers shell scripting. <xref linkend="ch-programming-c"/> covers C
+ programming. <xref linkend="ch-rpm-programming-python"/> covers Python scripting and programming,
+ and <xref linkend="ch-programming-perl"/> covers Perl scripting.
</para>
</sect1>
<sect1>
@@ -252,7 +252,7 @@
</para>
<para>
This script has a two-part command. The rpm ���qa part queries
- all RPM packages, as covered in Chapter 4. The grep rpm part
+ all RPM packages, as covered in <xref linkend="ch-using-rpm"/> . The grep rpm part
finds only packages with rpm in their names. This is a very
simple script, but it can serve to show how to work with
scripts.
@@ -267,7 +267,7 @@
<para>
If you���re new to Linux, you���ll notice there���s no program
named Notepad.exe. There are, though, a plethora of Linux text
- editors to choose from. See Appendix F for a listing of Linux
+ editors to choose from. See <xref linkend="ch-development-tools"/> for a listing of Linux
text-editing tools.
</para>
</sect2>
Index: rpm-guide-specfile-syntax-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfile-syntax-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-guide-specfile-syntax-en.xml 26 Oct 2005 01:54:11 -0000 1.2
+++ rpm-guide-specfile-syntax-en.xml 10 Nov 2005 22:30:07 -0000 1.3
@@ -149,14 +149,14 @@
</para>
<para>
Avoid percent signs, %, in comments, which may get interpreted
- as RPM macros. See Chapter 10 for details.
+ as RPM macros. See <xref linkend="ch-specfiles"/> for details.
</para>
</sect2>
<sect2>
<title>Build settings</title>
<para>
The BuildArchitectures tag names the architectures that a binary
- RPM will run on. See Chapter 21 for a description of the
+ RPM will run on. See <xref linkend="ch-customizing-rpm"/> for a description of the
architecture settings. A special value of noarch indicates a
package that is not dependent on a particular architecture, such
as a Perl or Python script.
@@ -180,7 +180,7 @@
<title>Dependency tags</title>
<para>
Dependency tags define all the dependencies for the package, as
- described in Chapter 6.
+ described in <xref linkend="ch-dependencies"/> .
</para>
<para>
For each dependency, you can specify a capability name alone.
@@ -324,7 +324,7 @@
Cross Reference
</para>
<para>
- See the section on Defining Macros in Spec Files in Chapter 21
+ See the section on Defining Macros in Spec Files in <xref linkend="ch-specfile-syntax"/>
for more on this subject.
</para>
<para>
Index: rpm-guide-specfiles-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-specfiles-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-specfiles-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-specfiles-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -196,7 +196,7 @@
<sect2>
<title>Storing spec files on disk</title>
<para>
- As discussed in Chapter 9, the rpmbuild command expands source
+ As discussed in <xref linkend="ch-creating-rpms"/> , the rpmbuild command expands source
RPMs to the /usr/src/redhat directory. Under this directory, the
RPM system assumes five subdirectories, listed in Table 10-1.
</para>
@@ -291,7 +291,7 @@
Cross Reference
</para>
<para>
- These directories are the default directories. See Chapter 21
+ These directories are the default directories. See <xref linkend="ch-specfile-syntax"/>
for changing RPM default values. In addition, these are the
defaults for &RHL;. See Chapters 19 and 20 for
discussions on other versions of Linux and other non-Linux
@@ -432,7 +432,7 @@
<para>
Many graphical installation tools divide packages by these
categories, so you want to fit into the existing group names
- if possible. (See Chapter 5 for more on querying group
+ if possible. (See <xref linkend="ch-using-rpm-db"/> for more on querying group
information from RPMs.) The official list of groups are
located in the file /usr/share/doc/rpm-4.1/GROUPS for RPM 4.1,
and in a similar location for other RPM versions.
@@ -822,7 +822,7 @@
Cross Reference
</para>
<para>
- Chapter 14 discusses packaging guidelines and best practices.
+ <xref linkend="ch-packaging-guidelines"/> discusses packaging guidelines and best practices.
Starting from pristine sources is one of the best practices.
</para>
<para>
@@ -849,7 +849,7 @@
Cross Reference
</para>
<para>
- Chapter 9 covers make and other Linux build tools.
+ <xref linkend="ch-creating-rpms"/> covers make and other Linux build tools.
</para>
<para>
In RPM terms, building the package is split into four steps:
@@ -907,7 +907,7 @@
<para>
Table 10-2 summarizes the %setup command-line parameters. Many
of these options apply mostly for subpackages, a topic covered
- in Chapter 11.
+ in <xref linkend="ch-advanced-packaging"/> .
</para>
<para>
Table 10-2 Command-line parameters for %setup
@@ -1215,7 +1215,7 @@
</para>
<para>
If you intend to support relocatable packages, covered in
- Chapter 11, you will likely need to pass a --prefix option to
+ <xref linkend="ch-advanced-packaging"/> , you will likely need to pass a --prefix option to
the configure script. For example:
</para>
<para>
@@ -1370,7 +1370,7 @@
Cross Reference
</para>
<para>
- Chapter 11 covers triggers, another form of script that gets run
+ <xref linkend="ch-advanced-packaging"/> covers triggers, another form of script that gets run
when packages are installed or removed.
</para>
<para>
@@ -1879,7 +1879,7 @@
Cross Reference
</para>
<para>
- See Chapter 5 for more on package verification.
+ See <xref linkend="ch-using-rpm-db"/> for more on package verification.
</para>
<para>
The %verify directive names the tests to include or not include.
@@ -2110,7 +2110,7 @@
</para>
<para>
You can also store this setting in a macro file so that it
- applies for all packages you build. See Chapter 21 for more on
+ applies for all packages you build. See <xref linkend="ch-customizing-rpm"/> for more on
macro files.
</para>
<para>
@@ -2475,7 +2475,7 @@
Cross Reference
</para>
<para>
- Chapter 15 covers shell scripting with RPM.
+ <xref linkend="ch-scripting"/> covers shell scripting with RPM.
</para>
<para>
With parameters, you can expand the normal definition of a macro
Index: rpm-guide-transactions-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-transactions-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-transactions-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-transactions-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -152,7 +152,7 @@
Cross Reference
</para>
<para>
- The gnorpm command is covered in Chapter 8. The rpmrebuild package
+ The gnorpm command is covered in <xref linkend="ch-management-software"/> . The rpmrebuild package
is covered in the "Saving Old Packages" section in this chapter.
</para>
<para>
@@ -322,7 +322,7 @@
Cross Reference
</para>
<para>
- Chapter 5 describes the --queryformat option.
+ <xref linkend="ch-using-rpm-db"/> describes the --queryformat option.
</para>
<para>
There is also a transaction ID for removal, the REMOVETID. You
@@ -494,12 +494,12 @@
</para>
<para>
Before running the --rollback option, backup your RPM database
- as described in Chapter 5.
+ as described in <xref linkend="ch-using-rpm-db"/> .
</para>
<para>
Because of all these limitations, rollbacks do not work in all
situations. In place of the --rollback option, you can use the
- query shortcuts introduced in Chapter 5 and find the packages
+ query shortcuts introduced in <xref linkend="ch-using-rpm-db"/> and find the packages
you have installed recently (if that is what you want to roll
back). In this case, you can use the rpm command to remove the
packages you want to get rid of and reinstall the packages you
Index: rpm-guide-using-rpm-db-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-db-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-using-rpm-db-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-using-rpm-db-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -64,7 +64,7 @@
<sect1>
<title>Querying the RPM Database</title>
<para>
- In Chapter 4, you saw that the rpm command usually takes one major
+ In <xref linkend="ch-using-rpm"/> , you saw that the rpm command usually takes one major
command-line option to tell it the operation to perform and a
myriad of command-line options to customize the operation. The rpm
command may also take the name of one or more RPM package files or
@@ -115,7 +115,7 @@
<para>
You can provide the whole package name to the rpm command, which
includes the name, the version, and the RPM package number, as
- discussed in Chapter 3. You can also just provide the name and
+ discussed in <xref linkend="ch-rpm-overview"/> . You can also just provide the name and
version number, as shown previously, or just the base name of
the package.
</para>
@@ -370,7 +370,7 @@
</para>
<para>
You can also use the --pipe option to the rpm command,
- introduced in Chapter 4. With this option, your command
+ introduced in <xref linkend="ch-using-rpm"/> . With this option, your command
becomes:
</para>
<para>
@@ -380,7 +380,7 @@
Cross Reference
</para>
<para>
- Chapter 17 covers programming with the RPM system with the
+ <xref linkend="ch-rpm-programming-python"/> covers programming with the RPM system with the
Python scripting language.
</para>
<para>
@@ -1479,7 +1479,7 @@
Cross Reference
</para>
<para>
- See Chapter 4 for more on installing RPMs.
+ See <xref linkend="ch-using-rpm"/> for more on installing RPMs.
</para>
</sect2>
<sect2>
@@ -2173,7 +2173,7 @@
A great many of the command-line options to the rpm command are
defined as popt aliases. These popt aliases define the rpm
command-line options in terms of longer query format strings.
- See Chapter 21 for more information on popt.
+ See <xref linkend="ch-customizing-rpm"/> for more information on popt.
</para>
<para>
You can add items to the query string and use C language
@@ -2309,7 +2309,7 @@
<title>Querying for Package Information</title>
<para>
Many of the query format tags refer to package-information
- data stored in the RPM header, introduced in Chapter 3. Table
+ data stored in the RPM header, introduced in <xref linkend="ch-rpm-overview"/> . Table
5-3 lists the package-information tags.
</para>
<para>
@@ -3493,7 +3493,7 @@
Cross Reference
</para>
<para>
- See Appendix D for a listing of all the tags in an RPM file.
+ See <xref linkend="ch-package-structure"/> for a listing of all the tags in an RPM file.
</para>
</sect3>
</sect2>
@@ -3678,9 +3678,9 @@
Querying Package Files Remotely
</para>
<para>
- As shown in Chapter 4, you can access RPM package files over a
+ As shown in <xref linkend="ch-using-rpm"/> , you can access RPM package files over a
network using FTP or HTTP connections. To query remote files, use
- the same rules as shown in Chapter 4, with the following syntax:
+ the same rules as shown in <xref linkend="ch-using-rpm"/> , with the following syntax:
</para>
<para>
rpm -qp ftp://username:password@hostname:port/path/to/rpm/file
@@ -4204,7 +4204,7 @@
Cross Reference
</para>
<para>
- Chapter 12 covers another option for verifying a package file,
+ <xref linkend="ch-rpmbuild"/> covers another option for verifying a package file,
the rpm ���K command.
</para>
<para>
@@ -4222,7 +4222,7 @@
<sect1>
<title>Working With the RPM Database</title>
<para>
- As mentioned in Chapter 3, the RPM database is stored in
+ As mentioned in <xref linkend="ch-rpm-overview"/> , the RPM database is stored in
/var/lib/rpm. The files in that directory are Berkeley DB files,
as shown by the file command:
</para>
Index: rpm-guide-using-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-en.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-guide-using-rpm-en.xml 31 Oct 2005 23:18:20 -0000 1.3
+++ rpm-guide-using-rpm-en.xml 10 Nov 2005 22:30:07 -0000 1.4
@@ -111,7 +111,7 @@
<para/>
<para>
Almost all installation steps use the rpm command with the ���U
- option, short for upgrade, as introduced in Chapter 3. The basic
+ option, short for upgrade, as introduced in <xref linkend="ch-rpm-overview"/> . The basic
syntax is:
</para>
<para>
@@ -144,7 +144,7 @@
</para>
<para>
This warning comes from the fact that the package was signed,
- but the key was not found. Chapter 12 covers signing packages.
+ but the key was not found. <xref linkend="ch-rpmbuild"/> covers signing packages.
In most cases, warnings such as this one are not that serious.
Errors, though, should be treated seriously.
</para>
@@ -1454,7 +1454,7 @@
configuration file on disk. This is where the rpm command
starts working with some upgrade rules. Note that this special
processing only applies to files marked as configuration files
- within the RPM. Chapter 10 covers how to mark files as
+ within the RPM. <xref linkend="ch-specfiles"/> covers how to mark files as
configuration files.
</para>
<para>
@@ -1689,7 +1689,7 @@
example, rarely come with source code. In this case, obviously,
no source RPMs are available. Or, a source RPM for a commercial
application may provide no source code, but still provide a way
- to build the resulting application. See Chapter 10 for more on
+ to build the resulting application. See <xref linkend="ch-specfiles"/> for more on
the source files and options for not including the sources in a
source RPM.
</para>
@@ -1992,7 +1992,7 @@
Cross Reference
</para>
<para>
- See Chapter 21 for more on the --showrc option.
+ See <xref linkend="ch-customizing-rpm"/> for more on the --showrc option.
</para>
<para>
The --version option tells the rpm command to print out the
18 years, 5 months