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-en.xml, 1.3, 1.4 rpm-guide-programming-python-en.xml, 1.4, 1.5 rpm-guide-rpmbuild-en.xml, 1.3, 1.4 rpm-guide-scripting-en.xml, 1.3, 1.4 rpm-guide-specfile-syntax-en.xml, 1.2, 1.3 rpm-guide-specfiles-en.xml, 1.3, 1.4 rpm-guide-transactions-en.xml, 1.3, 1.4 rpm-guide-using-rpm-db-en.xml, 1.3, 1.4 rpm-guide-using-rpm-en.xml, 1.3, 1.4
Stuart Ellis (elliss)
fedora-docs-commits at redhat.com
Thu Nov 10 22:30:14 UTC 2005
- Previous message: release-notes daemons-ru.xml, NONE, 1.1 database-servers-ru.xml, NONE, 1.1 desktop-ru.xml, NONE, 1.1 development-tools-ru.xml, NONE, 1.1 entertainment-ru.xml, NONE, 1.1 feedback-ru.xml, NONE, 1.1 file-servers-ru.xml, NONE, 1.1 file-systems-ru.xml, NONE, 1.1 hardware-reqs-ru.xml, NONE, 1.1 i18n-ru.xml, NONE, 1.1 install-notes-ru.xml, NONE, 1.1 intro-ru.xml, NONE, 1.1 java-package-ru.xml, NONE, 1.1 kernel-ru.xml, NONE, 1.1 legacynotice-ru.xml, NONE, 1.1 legacy-ru.xml, NONE, 1.1 legalnotice-content-ru.xml, NONE, 1.1 legalnotice-relnotes-ru.xml, NONE, 1.1 legalnotice-section-ru.xml, NONE, 1.1 misc-server-ru.xml, NONE, 1.1 multimedia-ru.xml, NONE, 1.1 networking-ru.xml, NONE, 1.1 overview-ru.xml, NONE, 1.1 package-movement-ru.xml, NONE, 1.1 package-notes-ru.xml, NONE, 1.1 printing-ru.xml, NONE, 1.1 project-overview-ru.xml, NONE, 1.1 RELEASE-NOTES-ru.xml, NONE, 1.1 samba-ru.xml, NONE, 1.1 security-ru.xml, NONE, 1.1 server-tools-ru.xml, NONE, 1.1 splash-ru.xml, NONE, 1.1 web-servers-ru.xml, NONE, 1.1 xorg-ru.xml, NONE, 1.1
- Next message: mirror-tutorial mirror-tutorial-en.xml,1.15,1.16
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
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
- Previous message: release-notes daemons-ru.xml, NONE, 1.1 database-servers-ru.xml, NONE, 1.1 desktop-ru.xml, NONE, 1.1 development-tools-ru.xml, NONE, 1.1 entertainment-ru.xml, NONE, 1.1 feedback-ru.xml, NONE, 1.1 file-servers-ru.xml, NONE, 1.1 file-systems-ru.xml, NONE, 1.1 hardware-reqs-ru.xml, NONE, 1.1 i18n-ru.xml, NONE, 1.1 install-notes-ru.xml, NONE, 1.1 intro-ru.xml, NONE, 1.1 java-package-ru.xml, NONE, 1.1 kernel-ru.xml, NONE, 1.1 legacynotice-ru.xml, NONE, 1.1 legacy-ru.xml, NONE, 1.1 legalnotice-content-ru.xml, NONE, 1.1 legalnotice-relnotes-ru.xml, NONE, 1.1 legalnotice-section-ru.xml, NONE, 1.1 misc-server-ru.xml, NONE, 1.1 multimedia-ru.xml, NONE, 1.1 networking-ru.xml, NONE, 1.1 overview-ru.xml, NONE, 1.1 package-movement-ru.xml, NONE, 1.1 package-notes-ru.xml, NONE, 1.1 printing-ru.xml, NONE, 1.1 project-overview-ru.xml, NONE, 1.1 RELEASE-NOTES-ru.xml, NONE, 1.1 samba-ru.xml, NONE, 1.1 security-ru.xml, NONE, 1.1 server-tools-ru.xml, NONE, 1.1 splash-ru.xml, NONE, 1.1 web-servers-ru.xml, NONE, 1.1 xorg-ru.xml, NONE, 1.1
- Next message: mirror-tutorial mirror-tutorial-en.xml,1.15,1.16
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the docs-commits
mailing list