rpm-guide rpm-guide-using-rpm-en.xml,1.5,1.6
Stuart Ellis (elliss)
fedora-docs-commits at redhat.com
Sun Nov 20 19:20:23 UTC 2005
Author: elliss
Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24834
Modified Files:
rpm-guide-using-rpm-en.xml
Log Message:
Tagged to FDP standards.
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.5 -r 1.6 rpm-guide-using-rpm-en.xml
Index: rpm-guide-using-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- rpm-guide-using-rpm-en.xml 14 Nov 2005 21:55:05 -0000 1.5
+++ rpm-guide-using-rpm-en.xml 20 Nov 2005 19:20:15 -0000 1.6
@@ -27,19 +27,20 @@
installing a package, but there’s a lot more you can do. For
example, you can install packages from remote sites using HTTP or
FTP to download the package to install. There are quite a few other
- rpm options you can use to get information and feedback on
- installation, for example.
+ <command>rpm</command> options you can use to get information and
+ feedback on installation, for example.
</para>
<sect1>
- <title>The rpm Command</title>
+ <title>The <command>rpm</command> Command</title>
<para>
- Just about everything you do with RPM requires the rpm command. As
- a nice added benefit, just about everything you do with RPM
- requires a single invocation of the rpm command. That means common
- tasks such as installing and removing software can be done quickly
- and efficiently. The basics of the rpm command are not very hard,
- and you can perform the basic tasks within a few minutes of
- reading this chapter.
+ Just about everything you do with RPM requires the
+ <command>rpm</command> command. As a nice added benefit, just
+ about everything you do with RPM requires a single invocation of
+ the <command>rpm</command> command. That means common tasks such
+ as installing and removing software can be done quickly and
+ efficiently. The basics of the <command>rpm</command> command are
+ not very hard, and you can perform the basic tasks within a few
+ minutes of reading this chapter.
</para>
</sect1>
<sect1>
@@ -47,19 +48,20 @@
<para>
To install software, you need something to install. Typically,
this is a file packaged as RPM, using a file-name extension of
- .rpm. Of course, this isn’t required, but just about every RPM
- package is stored in a file with a .rpm extension. For example,
- the following file holds an RPM package, ready to be installed:
+ <filename>rpm</filename>. Of course, this isn’t required, but
+ just about every RPM package is stored in a file with a
+ <filename>rpm</filename> extension. For example, the following
+ file holds an RPM package, ready to be installed:
</para>
<para>
- jikes-1.16-1.i386.rpm
+ <filename>jikes-1.16-1.i386.rpm</filename>
</para>
<para>
- This package holds an application named jikes (a Java language
- compiler application). From the discussion in the last two
- chapters, you should be able to determine the version of the
- program this RPM holds and which release of the RPM package this
- represents.
+ This package holds an application named <command>jikes</command>
+ (a Java language compiler application). From the discussion in the
+ last two chapters, you should be able to determine the version of
+ the program this RPM holds and which release of the RPM package
+ this represents.
</para>
<para>
Other RPMs hold sources, the program source codes used to create
@@ -67,194 +69,218 @@
file holds a source RPM:
</para>
<para>
- jikes-1.16-1.src.rpm
+ <filename>jikes-1.16-1.src.rpm</filename>
</para>
<para>
- The src in the package name is short for source. This file-naming
- convention is not required, but is used by just about all source
- code packages. (Following conventions helps other administrators
- know what to expect.)
- </para>
- <para>
- Cross Reference
- </para>
- <para>
- <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
- installing packages:
- </para>
- <para>
- An upgrade operation means installing a new version of a package
- and removing all previous versions of the same package. If you
- have not installed a package previously, the upgrade operation
- will install the package.
- </para>
- <para>
- A freshen operation means to install a new version of a package
- only if you have already installed another version of the package.
- </para>
- <para>
- An install operation installs a package for the first time. It
- also, through special command-line parameters, allows you to
- install multiple versions of a package, usually not what you want.
- So, in the vast majority of cases, you want to run the upgrade
- operation for all package installations.
+ The <filename>src</filename> in the package name is short for
+ source. This file-naming convention is not required, but is used
+ by just about all source code packages. (Following conventions
+ helps other administrators know what to expect.)
</para>
+ <note>
+ <title>Building Packages from Source RPMs</title>
+
+ <para>
+ Refer to <xref linkend="ch-creating-rpms"/> and
+ <xref linkend="ch-rpmbuild"/> for information on building RPMs
+ from source RPMs.
+ </para>
+ </note>
+ <para>
+ The <command>rpm</command> command provides three main operations
+ for upgrading and installing packages:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Upgrade</term>
+ <listitem>
+ <para>
+ An upgrade operation means installing a new version of a
+ package and removing all previous versions of the same
+ package. If you have not installed a package previously, the
+ upgrade operation will install the package.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Freshen</term>
+ <listitem>
+ <para>
+ A freshen operation means to install a new version of a
+ package only if you have already installed another version
+ of the package.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Install</term>
+ <listitem>
+ <para>
+ An install operation installs a package for the first time.
+ It also, through special command-line parameters, allows you
+ to install multiple versions of a package, usually not what
+ you want. So, in the vast majority of cases, you want to run
+ the upgrade operation for all package installations.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
<para>
The following sections cover the command-line options that apply
to these operations.
</para>
<sect2>
- <title>Upgrading with the rpm command</title>
+ <title>Upgrading with the <command>rpm</command> command</title>
<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:
+ Almost all installation steps use the <command>rpm</command>
+ command with the <option>–U</option> option, short for
+ upgrade, as introduced in <xref linkend="ch-rpm-overview"/> .
+ The basic syntax is:
</para>
<para>
- rpm -U package_name
+ <command>rpm</command> <option>-U</option>
+ <replaceable>package_name</replaceable>
</para>
<para>
For example:
</para>
<para>
- rpm –i jikes-1.16-1.i386.rpm
+<screen>
+<userinput>rpm –i jikes-1.16-1.i386.rpm</userinput>
+</screen>
</para>
<para>
- You can also use the --upgrade long option in place of -U.
+ You can also use the <option>--upgrade</option> long option in
+ place of <option>-U</option>.
[...2990 lines suppressed...]
+ <filename>rc</filename> settings.
+ </para>
+ </note>
+ <note>
+ <title>The <option>--showrc</option> Option</title>
+
+ <para>
+ See <xref linkend="ch-customizing-rpm"/> for more on the
+ <option>--showrc</option> option.
+ </para>
+ </note>
<para>
- /usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:/etc/rpmrc:~/.rpmrc
- </para>
- <para>
- Note
- </para>
- <para>
- The ~/.rpmrc means to look in the user's home directory for a file
- named .rpmrc.
- </para>
- <para>
- You can use the --showrc option to list all the rc settings.
- </para>
- <para>
- Cross Reference
- </para>
- <para>
- 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
- version number of the command and then exit. For example:
- </para>
- <para>
- rpm --version
- </para>
+ The <option>--version</option> option tells the
+ <command>rpm</command> command to print out the version number of
+ the command and then exit. For example:
+ </para>
+<screen>
+<userinput>rpm --version</userinput>
+</screen>
<para>
This command prints out a version number, like the following:
</para>
+<screen>
+<computeroutput>RPM version 4.1</computeroutput>
+</screen>
<para>
- RPM version 4.1
- </para>
- <para>
- The --dbpath option, mentioned previously, tells the rpm command
- to use a different RPM database. This is useful when testing a
- complete system install, where you want to change the RPM database
- but don't want that to affect your running Linux system. In this
- case, you can use a different RPM database and test out your
- changes. The basic syntax for this option is:
+ The <option>--dbpath</option> option, mentioned previously, tells
+ the <command>rpm</command> command to use a different RPM
+ database. This is useful when testing a complete system install,
+ where you want to change the RPM database but don't want that to
+ affect your running Linux system. In this case, you can use a
+ different RPM database and test out your changes. The basic syntax
+ for this option is:
</para>
<para>
- --dbpath directory_name
+ <option>--dbpath</option>
+ <replaceable>directory_name</replaceable>
</para>
<para>
- The --pipe option tells the rpm command to send, or pipe, its
- output to another program. The syntax for this option is:
+ The <option>--pipe</option> option tells the
+ <command>rpm</command> command to send, or pipe, its output to
+ another program. The syntax for this option is:
</para>
<para>
- --pipe command_to_send_out_to
+ <option>--pipe</option>
+ <replaceable>command_to_send_out_to</replaceable>
</para>
</sect1>
<sect1>
@@ -2035,40 +2023,38 @@
common actions of installing, removing, and upgrading software.
</para>
<para>
- The rpm –e command removes packages. The rpm –U command
+ The <command>rpm</command> <option>–e</option> command removes
+ packages. The <command>rpm</command> <option>–U</option> command
upgrades packages by installing new packages and removing old
versions of all the packages upgraded. RPM upgrades also work for
- installing new packages. The rpm –F command freshens packages.
- This command only upgrades a package if an older version of the
- package has already been installed. The rpm –i command installs
- packages.
- </para>
- <para>
- Table 4-3 summarizes the rpm command-line options for installing,
- removing, and upgrading packages.
+ installing new packages. The <command>rpm</command>
+ <option>–F</option> command freshens packages. This command only
+ upgrades a package if an older version of the package has already
+ been installed. The <command>rpm</command> <option>–i</option>
+ command installs packages.
</para>
<para>
- Table 4-3 Installing, Removing, and Upgrading with the rpm command
- </para>
- <informaltable frame="all">
+ The table below summarizes the <command>rpm</command> command-line
+ options for installing, removing, and upgrading packages.
+ </para>
+ <table id="tb-rpm-command-options">
+ <title>Installing, Removing, and Upgrading with the <command>rpm</command>
+ command</title>
+ <colspec colnum="1" colname="Command"/>
+ <colspec colnum="2" colname="Usage"/>
<tgroup cols="2">
- <tbody>
+ <thead>
<row>
- <entry>
- <para>
- Command
- </para>
- </entry>
- <entry>
- <para>
- Usage
- </para>
- </entry>
+ <entry>Command</entry>
+ <entry>Usage</entry>
</row>
+ </thead>
+ <tbody>
<row>
<entry>
<para>
- rpm –i install_options package_files
+ <command>rpm –i <replaceable>install_options
+ package_files</replaceable></command>
</para>
</entry>
<entry>
@@ -2080,7 +2066,8 @@
<row>
<entry>
<para>
- rpm –e remove_options packages
+ <command>rpm –e <replaceable>remove_options
+ packages</replaceable></command>
</para>
</entry>
<entry>
@@ -2092,7 +2079,8 @@
<row>
<entry>
<para>
- rpm –U install_options package_files
+ <command>rpm –U <replaceable>install_options
+ package_files</replaceable></command>
</para>
</entry>
<entry>
@@ -2105,7 +2093,8 @@
<row>
<entry>
<para>
- rpm –Uvh install_options package_files
+ <command>rpm –Uvh <replaceable>install_options
+ package_files</replaceable></command>
</para>
</entry>
<entry>
@@ -2118,7 +2107,8 @@
<row>
<entry>
<para>
- rpm –F install_options package_files
+ <command>rpm –F <replaceable>install_options
+ package_files</replaceable></command>
</para>
</entry>
<entry>
@@ -2129,7 +2119,7 @@
</row>
</tbody>
</tgroup>
- </informaltable>
+ </table>
<para>
Unfortunately, modern system management gets more complex than
that. The next chapter delves into package dependencies and the
More information about the docs-commits
mailing list