Author: elliss

Update of /cvs/docs/yum-software-management In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3215

Modified Files: Makefile yum-software-management-en.xml Log Message:

- Update Makefile to use Makefile.common - Amended to cover auto GPG key import - Added section on localinstall

Index: Makefile =================================================================== RCS file: /cvs/docs/yum-software-management/Makefile,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- Makefile 29 Jun 2005 00:41:23 -0000 1.3 +++ Makefile 9 Jul 2005 15:06:36 -0000 1.4 @@ -1,30 +1,30 @@ ############################################################################### # Makefile for RHLP docs project # Created by: Tammy Fox tfox@redhat.com -# Last edited by: Stuart Ellis stuart@elsn.org +# Last edited by: Tommy Reynolds Tommy.Reynolds@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 = yum-software-management-$(LANG) -XMLFILE = $(DOCNAME).xml +XSLPDF = ../docs-common/xsl/main-pdf.xsl +XSLHTML = ../docs-common/xsl/main-html.xsl +XSLHTMLNOCHUNKS = ../docs-common/xsl/main-html-nochunks.xsl +LANG = en +DOCNAME = yum-software-management-$(LANG) +XMLFILE = $(DOCNAME).xml +XMLEXTRAFILES = + ###################################################### 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

View full diff with command: /usr/bin/cvs -f diff -kk -u -N -r 1.5 -r 1.6 yum-software-management-en.xml Index: yum-software-management-en.xml =================================================================== RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- yum-software-management-en.xml 22 Jun 2005 00:07:32 -0000 1.5 +++ yum-software-management-en.xml 9 Jul 2005 15:06:36 -0000 1.6 @@ -4,1139 +4,1318 @@ <!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent"> %FEDORA-ENTITIES-EN;

-<!ENTITY BOOKID "yum-software-management-0.4.4 (2005-06-14)"> <!-- change version of manual and date here --> +<!ENTITY BOOKID "yum-software-management-0.5.0 (2005-07-09)"> <!-- change version of manual and date here -->

<!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">

<!-- Bugzilla bug number for the draft notice --> <!ENTITY BUG-NUM "155190"> -<!ENTITY FCLOCALVER "3"> +<!ENTITY FCLOCALVER "4"> <!ENTITY DRAFTNOTICE SYSTEM "../docs-common/common/draftnotice-en.xml">

]>

- <article id="yum-software-management" lang="en"> - <articleinfo> - <title>Software Management with <command>yum</command></title> - <copyright> - <year>2005</year> - <holder>Stuart Ellis</holder> - </copyright> - <authorgroup> - <author> - <surname>Ellis</surname> - <firstname>Stuart</firstname> - </author> - </authorgroup> +<article id="yum-software-management" lang="en"> + <articleinfo> + <title>Software Management with <command>yum</command></title> + <copyright> + <year>2005</year> + <holder>Stuart Ellis</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> - Initial import into CVS. + <revnumber>0.4</revnumber> + <date>2005-06-01</date> + <authorinitials>StuartEllis</authorinitials> + <revdescription> + <para> + Initial import into CVS. </para> - </revdescription> - </revision> + </revdescription> + </revision> </revhistory> - </articleinfo> - + </articleinfo>

<section id="sn-introduction"> - <title>Introduction</title> - + <title>Introduction</title> &DRAFTNOTICE; + <section id="sn-software-management-audience"> + <title>Audience</title>

- <section id="sn-software-management-audience"> - <title>Audience</title> - <para> - The <command>yum</command> utility is currently the recommended method for - managing software on &FED; systems. All &FED; users responsible for - maintaining their own systems will find <command>yum</command> an essential tool. - </para> - </section> - - <section id="sn-software-management-usingdoc"> - <title>Using This Document</title> - <para> - This document is a reference for using <command>yum</command>. You may - wish to read some or all of the sections, depending upon your needs and - level of experience. - </para> - <para> - If you are a new user, read the <xref - linkend="sn-software-management-concepts"/> before using - <command>yum</command> for the first time. - </para> - <para> - Experienced Linux users should start with <xref linkend="sn-authorizing-package-sources"/>. - </para> - <para> - Anyone with several &FED; systems on a network may benefit from setting - up their own software repositories to manage the process of installation and - updates. The details of maintaining your own repositories are explained - in <xref linkend="sn-managing-repositories"/>. - </para> - <para> - Most of the examples use the package <filename>tsclient</filename>, - which is included with &FC; to provide an application for remote desktop - access. If it is installed successfully you may start the application - by choosing - <menuchoice><guimenu>Applications</guimenu><guisubmenu>Internet</guisubmenu><guimenuitem>Terminal - Server Client</guimenuitem></menuchoice>. To use the examples, - substitute the name of the relevant package for <filename>tsclient</filename>. - </para> - <important> - <title>Avoid Logging in with the Root Account</title> - <para> - You do not need to log in with the root account in order to manage your - &FC; system. All of the commands shown in this tutorial that require - root access will prompt you for the root password. The example - terminal commands use <command>su <option>-c</option></command> to - provide this facility. - </para> - </important> - </section> + <para> + The <command>yum</command> utility is currently the recommended + method for managing software on &FED; systems. All &FED; users + responsible for maintaining their own systems will find + <command>yum</command> an essential tool. + </para> + </section>

+ <section id="sn-software-management-usingdoc"> + <title>Using This Document</title>

- <section id="sn-yum-additional-resources"> - <title>Additional Resources</title> - <indexterm> - <primary>yum, documentation</primary> - </indexterm> - <indexterm> - <primary>yum, man pages</primary> - </indexterm> - <para> - The <command>yum</command> utility has features and options that - are not discussed in this document. Read the <command>man</command> pages - for <command>yum(8)</command> and <filename>yum.conf(5)</filename> to - learn more. - </para> - <indexterm> - <primary>yum, Websites</primary> - </indexterm> - <para> - The official Website for <command>yum</command> is: - </para> - <para> - <ulink url="http://linux.duke.edu/projects/yum/">http://linux.duke.edu/projects/yum/</ulink> - </para> - <indexterm> - <primary>Yum, mailing lists</primary> - </indexterm> - <para> - The official mailing list for <command>yum</command> users is: - </para> - <para> - <ulink url="https://lists.dulug.duke.edu/mailman/listinfo/yum">https://lists.dulug.duke.edu/mailman/listinfo/yum</ulink> - </para> - <para> - The archive for the <command>yum</command> development mailing list is here: - </para> - <para> - <ulink url="https://lists.dulug.duke.edu/pipermail/yum-devel/">https://lists.dulug.duke.edu/pipermail/yum-devel/</ulink> - </para> + <para> + This document is a reference for using <command>yum</command>. + You may wish to read some or all of the sections, depending upon + your needs and level of experience. + </para> + + <para> + If you are a new user, read the + <xref + linkend="sn-software-management-concepts"/> before + using <command>yum</command> for the first time. + </para> + + <para> + Experienced Linux users should start with + <xref linkend="sn-updating-your-system"/>. + </para> [...2082 lines suppressed...] </section>

<section id="sn-updating-repository"> - <title>Updating a Repository</title> - <indexterm> - <primary>repositories, updating</primary> - </indexterm> - <para> - Whenever a package is added, or replaced with a different version, you - must run <command>createrepo</command> again for the index files to be updated. - If you are mirroring an existing repository then you may assume that - the site administrator updates the indexes, but for safety you should - add this to your synchronization scripts. The - <command>createrepo</command> utility can be run as frequently as you wish. + <title>Updating a Repository</title> + <indexterm> + <primary>repositories, updating</primary> + </indexterm> + <para> + Whenever a package is added, or replaced with a different + version, you must run <command>createrepo</command> again for + the index files to be updated. If you are mirroring an existing + repository then you may assume that the site administrator + updates the indexes, but for safety you should add this to your + synchronization scripts. The <command>createrepo</command> + utility can be run as frequently as you wish. </para> - </section> - + </section> </section>

- - <section id="sn-yum-proxy-server"> - <title>Using <command>yum</command> with a Proxy Server</title> - <indexterm> + <section id="sn-yum-proxy-server"> + <title>Using <command>yum</command> with a Proxy Server</title> + <indexterm> <primary>proxy server, with yum</primary> - </indexterm> - <indexterm> + </indexterm> + <indexterm> <primary>yum, using a proxy server</primary> - </indexterm> - <para> - Repositories may be accessed through standard proxy servers. If your - system is connected to the Internet through a Web proxy server, specify - the details of the server in <filename>/etc/yum.conf</filename>. The - <command>proxy</command> 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 - <command>proxy_username</command> and <command>proxy_password</command> settings. - </para> - - <para> - For example, the settings below enable <command>yum</command> to use the - proxy server <command>mycache.mydomain.com</command>, connecting to port - <command>3128</command>, with the username <command>yum-user</command> and the password <command>qwerty</command>. - </para> + </indexterm> + <para> + Repositories may be accessed through standard proxy servers. If + your system is connected to the Internet through a Web proxy + server, specify the details of the server in + <filename>/etc/yum.conf</filename>. The <command>proxy</command> + 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 + <command>proxy_username</command> and + <command>proxy_password</command> settings. + </para> + + <para> + For example, the settings below enable <command>yum</command> to + use the proxy server <command>mycache.mydomain.com</command>, + connecting to port <command>3128</command>, with the username + <command>yum-user</command> and the password + <command>qwerty</command>. + </para>

- <example id="config-file-httpproxy"> + <example id="config-file-httpproxy"> <title>Configuration File Settings for Using A Proxy Server</title> - <programlisting> +<programlisting> <![CDATA[ # The proxy server - proxy server:port number proxy=http://mycache.mydomain.com:3128 @@ -1213,64 +1398,70 @@ proxy_password=qwerty ]]> </programlisting> - </example> + </example>

- <note> + <note> <title>Global Settings</title> + <para> - Defining a proxy server in <filename>/etc/yum.conf</filename> means that - <emphasis>all</emphasis> users connect to the proxy server with those - details when using <command>yum</command>. - </para> - </note> - - <para> - To enable proxy access for a specific user, add the lines in the - example box below to their 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 <command>mycache.mydomain.com</command>, connecting to port <command>3128</command>. - </para> - <example id="profile-script-httpproxy"> + Defining a proxy server in <filename>/etc/yum.conf</filename> + means that <emphasis>all</emphasis> users connect to the proxy + server with those details when using <command>yum</command>. + </para> + </note> + + <para> + To enable proxy access for a specific user, add the lines in the + example box below to their 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 + <command>mycache.mydomain.com</command>, connecting to port + <command>3128</command>. + </para> + + <example id="profile-script-httpproxy"> <title>Profile Settings for Using a Proxy Server</title> - <programlisting> +<programlisting> <![CDATA[ # The Web proxy server used by this account http_proxy="http://mycache.mydomain.com:3128" export http_proxy ]]> </programlisting> - </example> + </example> + + <para> + If the proxy server requires a username and password then add + these to the URL. For example, to include the username + <command>yum-user</command> and the password + <command>qwerty</command>: + </para>

- <para> - If the proxy server requires a username and password then add these to the - URL. For example, to include the username - <command>yum-user</command> and the password <command>qwerty</command>: - </para> - <example id="profile-script-httpproxy-withpassword"> + <example id="profile-script-httpproxy-withpassword"> <title>Profile Settings for a Secured Proxy Server</title> - <programlisting> +<programlisting> <![CDATA[ # 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 ]]> </programlisting> - </example> - <note> - <title><command>http_proxy</command> Variable with Other Utilities</title> - <para> - The <command>http_proxy</command> 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> + </example>

- </section> + <note> + <title><command>http_proxy</command> Variable with Other Utilities</title>

+ <para> + The <command>http_proxy</command> 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>

-<index id="generated-index"></index> + <index id="generated-index"></index> </article> - -