Библиотека сайта rus-linux.net
This section outlines the tags that comprise a spec file's preamble.
This section outlines the tags that are used to name a package.
The
%description tag is used to define an in-depth
description of the packaged software. In the descriptive text, a
space in the first column indicates that that line of text should be
presented to user as-is, with no formatting done by RPM. Blank lines
in the descriptive text denote paragraphs.
%description
It slices!
It dices!
It's a CD player app that can't be beat.
By using the resonant frequency of the CD itself, it is able to simulate
20X oversampling. This leads to sound quality that cannot be equaled with
more mundane software...
|
The
%description tag can be made specific to a
particular subpackage by adding the subpackage name, and optionally,
the
-n option:
%description bar
%description -n bar
|
The subpackage name and usage of the -n option must
match those defined with the %package directive.
See also: the section called The %description Tag in Chapter 13.
The
Icon: tag is used to name a file containing an
icon representing the packaged software. The file may be in either
GIF or XPM format, although XPM is preferred. In either case, the
background of the icon should be transparent.
See also: the section called The icon Tag in Chapter 13.
The
URL: tag is used to define a Uniform Resource
Locator that can be used to obtain additional information about the
packaged software.
URL: http://www.gnomovision.com/cdplayer.html
|
See also: the section called The url Tag in Chapter 13.
The
Requires: tag is used to alert RPM to the fact
that the package needs to have certain capabilities available in order
to operate properly.
A version may be specified, following the package specification. The
following comparison operators may be placed between the package and
version:
Requires: playmidi >= 2.3
|
If the
Requires: tag needs to perform a comparison
against a serial numbered defined with the
Serial:
tag, then the proper format would be:
See also: the section called The requires Tag in Chapter 13.
The
Conflicts: tag is used to alert RPM to the fact
that the package is not compatible with other packages.
A version may be specified, following the package specification. The
following comparison operators may be placed between the package and
version:
Conflicts: playmidi >= 2.3
|
If the
Conflicts: tag needs to perform a comparison
against a serial numbered defined with the
Serial:
tag, then the proper format would be:
See also: the section called The conflicts Tag in Chapter 13.
The
AutoReqProv: tag is used to control the
automatic dependency processing performed when the package is being
built. To disable automatic dependency processing, add the following
line:
(The number 0 may be used instead of
no) Although RPM defaults to performing automatic
dependency processing, the effect of the
AutoReqProv: tag can be reversed by changing
no to yes. (The number
1 may be used instead of yes)
See also: the section called The autoreqprov Tag in Chapter 13.
The
Prefix: tag is used to define part of the path
RPM will use when installing the package's files. The prefix can be
redefined by the user when the package is installed, thereby changing
where the package is installed.
See also: the section called The prefix Tag in Chapter 13.
The Source: tag is used to define the filename of
the sources to be packaged. When there is more than one
Source: tag in a spec file, each one must be
numbered so they are unique, starting with the number
0. When there is only one tag, it does not need to
be numbered.
By convention, the source filename is usually preceded by a URL
pointing to the location of the original sources, but RPM does not
require this.
Source0: ftp://ftp.gnomovision.com/pub/cdplayer-1.0.tgz
Source1: foo.tgz
|
See also: the section called The source Tag in Chapter 13.
The
NoSource: tag is used to alert RPM to the fact
that one or more source files should be excluded from the source
package file. The tag is followed by one or more numbers. The
numbers correspond to the numbers following the
Source: tags that are to be excluded from packaging.
See also: the section called The nosource Tag in Chapter 13.
The
Patch: tag is used to define the name of a patch
file to be applied to the package's sources. When there is more than
one
Patch: tag in a spec file, each one must be
numbered so they are unique, starting with the number
0. When there is only one tag, it does not need to
be numbered.
Patch: cdp-0.33-fsstnd.patch
|
See also: the section called The patch Tag in Chapter 13.
The
NoPatch: tag is used to alert RPM to the fact
that one or more patch files should be excluded from the source
package file. The tag is followed by one or more numbers. The
numbers correspond to the numbers following the
Patch: tags that are to be excluded from packaging.
See also: the section called The nopatch Tag in Chapter 13.
