appendix-b.html

linux-unix130.linux.and.unix.ebooks130 linux and unix ebookslinuxLearning Linux - Collection of 12 E

<P>The format of the buildostranslate entry is slightly different from most other
rpmrc file entries. Instead of the usual
&lt;name&gt;:&lt;value&gt; format, the
buildostranslate entry looks like this:
</P>
<!-- CODE SNIP //-->
<PRE>
buildostranslate:&lt;label&gt;: &lt;string&gt;
</PRE>
<!-- END CODE SNIP //-->

<P>&lt;label&gt; is compared against information from
uname(2). If a match is found, &lt;string&gt; is
used by RPM to define the build operating system.
</P>

<H4>
B.4.5. arch_compat
</H4>

<P>The arch_compat entry is used to define which architectures are compatible with one
another. This information is used when packages are installed; in this way, RPM can determine
whether a given package file is compatible with the system. The format of the entry is
</P>
<!-- CODE SNIP //-->
<PRE>
arch_compat:&lt;label&gt;: &lt;list&gt;
</PRE>
<!-- END CODE SNIP //-->

<P>&lt;label&gt; is an architecture string, as defined by an
arch_canon entry. &lt;list&gt; following it
consists of one or more architectures, also defined by
arch_canon. If there is more than one architecture in the list, they should be separated by a space.
</P>

<P>The architectures in the list are considered compatible to the architecture specified in the label.
</P>

<H4>
B.4.6. os_compat
</H4>

<P>Default value: (operating system specific)
</P>

<P>The os_compat entry is used to define which operating systems are compatible with one
another. This information is used when packages are installed; in this way, RPM can
determine whether a given package file is compatible with the system. The format of the entry is
</P>
<!-- CODE SNIP //-->
<PRE>
&lt;name&gt;:&lt;label&gt;: &lt;list&gt;
</PRE>
<!-- END CODE SNIP //-->

<A NAME="PAGENUM-361"><P>Page 361</P></A>

<P>&lt;label&gt; is an operating system string, as defined by an
os_canon entry. &lt;list&gt; following it consists of one or more operating systems, also defined by
os_canon. If there is more than one operating system in the list, they should be separated by a space.
</P>

<P>The operating systems in the list are considered compatible to the operating system
specified in the label.
</P>

<H4>
B.4.7. builddir
</H4>

<P>Default value: (topdir)/BUILD
</P>

<P>The builddir entry is used to define the path to
the directory in which RPM will build packages. Its default value is taken from the value of the
topdir entry, with /BUILD appended to it. Note that if you redefine
builddir, you'll need to specify a complete path.
</P>

<H4>
B.4.8. buildroot
</H4>

<P>Default value: (none)
</P>

<P>The buildroot entry defines the path used as the root directory during the install phase of
a package build. For more information on using build roots, see Chapter 16, &quot;Making a
Package That Can Build Anywhere,&quot; specifically section 16.1.
</P>

<H4>
B.4.9. cpiobin
</H4>

<P>Default value: cpio
</P>

<P>The cpiobin entry is used to define the name (and optionally, the path) of the
cpio program. RPM uses cpio to perform a variety of functions, and needs to know where the program can
be found.
</P>

<H4>
B.4.10. dbpath
</H4>

<P>Default value: /var/lib/rpm
</P>

<P>The dbpath entry is used to define the directory in which the RPM database files are stored.
It can be overridden by using the --dbpath option on the RPM command line.
</P>

<H4>
B.4.11. defaultdocdir
</H4>

<P>Default value: /usr/doc
</P>

<P>The defaultdocdir entry is used to define the directory in which RPM will store
documentation for all installed packages. It is used only during builds to support the
%doc directive.
</P>

<A NAME="PAGENUM-362"><P>Page 362</P></A>



<H4>
B.4.12. distribution
</H4>

<P>Default value: (none)
</P>

<P>The distribution entry is used to define the distribution for each package. The
distribution can also be set by adding the
distribution tag to a particular spec file. The
distribution tag in the spec file overrides the distribution
rpmrc file entry.
</P>

<H4>
B.4.13. excludedocs
</H4>

<P>Default value: 0
</P>

<P>The excludedocs entry is used to control if documentation should be written to disk when
a package is installed. By default, documentation is installed; however, this can be overridden
by setting the value of excludedocs to 1. Note also that the
--excludedocs and --includedocs options can be added to the RPM command line to override the
excludedocs entry's behavior. For more information on the
--excludedocs and --includedocs options, please refer to Chapter
2, &quot;Using RPM to Install Packages.&quot;
</P>

<H4>
B.4.14. ftpport
</H4>

<P>Default value: (none)
</P>

<P>The ftpport entry is used to define the port RPM should use when manipulating package
files via FTP. See Chapter 2 for more information on how FTP ports are used by RPM.
</P>

<H4>
B.4.15. ftpproxy
</H4>

<P>Default value: (none)
</P>

<P>The ftpproxy entry is used to define the hostname of the FTP proxy system RPM should
use when manipulating package files via FTP. See Chapter 2 for more information on how
FTP proxy systems are used by RPM.
</P>

<H4>
B.4.16. messagelevel
</H4>

<P>Default value: 3
</P>

<P>The messagelevel entry is used to define the desired verbosity level. Levels less than
3 produce greater amounts of output, while levels greater than
3 produce less output.
</P>

<H4>
B.4.17. netsharedpath
</H4>

<P>Default value: (none)
</P>

<A NAME="PAGENUM-363"><P>Page 363</P></A>



<P>The netsharedpath entry is used to define one or more paths that, on the local system, are
shared with other systems. If more than one path is specified, they must be separated with colons.
</P>

<H4>
B.4.18. optflags
</H4>

<P>Default value: (architecture specific)
</P>

<P>The optflags entry is used to define a standard set of options that can be used during the
build process, specifically during compilation.
</P>

<P>The format of the optflags entry is slightly different from most other
rpmrc file entries. Instead of the usual
&lt;name&gt;:&lt;value&gt; format, the optflags entry looks like this:
</P>
<!-- CODE SNIP //-->
<PRE>
optflags:&lt;architecture&gt; &lt;value&gt;
</PRE>
<!-- END CODE SNIP //-->

<P>For example, assume the following optflags entries were placed in an
rpmrc file:
</P>
<!-- CODE SNIP //-->
<PRE>
optflags: i386 -O2 -m486 -fno-strength-reduce
optflags: sparc -O2
</PRE>
<!-- END CODE SNIP //-->

<P>If RPM was running on an Intel 80386_compatible architecture, the
optflags value would be set to -O2 -m486
-fno-strength-reduce. If, however, RPM was running on a Sun
SPARC_based system, optflags would be set to -O2.
</P>

<P>This entry sets the RPM_OPT_FLAGS environment variable, which can be used in the
%prep, %build, and %install scripts.
</P>

<H4>
B.4.19. packager
</H4>

<P>Default value: (none)
</P>

<P>The packager entry is used to define the name and contact information for the individual
responsible for building the package. The contact information is traditionally defined in the
following format:
</P>

<!-- CODE SNIP //-->
<PRE>
packager:Erik Troan &lt;[e-mail]&gt;
</PRE>
<!-- END CODE SNIP //-->

<H4>
B.4.20. pgp_name
</H4>

<P>Default value: (none)
</P>

<P>The pgp_name entry is used to define the name of the PGP public key that will be used to
sign each package built. The value is not case sensitive, but the key name entered here must
match the actual key name in every other aspect.
</P>

<P>For more information on signing packages with PGP, please read Chapter 17, &quot;Adding
PGP Signatures to a Package.&quot;
</P>

<A NAME="PAGENUM-364"><P>Page 364</P></A>



<H4>
B.4.21. pgp_path
</H4>

<P>Default value: (none)
</P>

<P>The pgp_path entry is used to point to a directory containing PGP keyring files. These files
will be searched for the public key specified by the
pgp_name entry.
</P>

<P>For more information on signing packages with PGP, see Chapter 17.
</P>

<H4>
B.4.22. require_distribution
</H4>

<P>Default value: 0
</P>

<P>The require_distribution entry is used to direct RPM to require that every package built must contain distribution information. The default value directs RPM to not enforce this requirement. If the entry has a non-zero value, RPM will only build packages that define
a distribution.
</P>

<H4>
B.4.23. require_icon
</H4>

<P>Default value: 0
</P>

<P>The require_icon entry is used to direct RPM to require that every package built must
contain an icon. The default value directs RPM to not enforce this requirement. If the entry has a
non-zero value, RPM will only build packages that contain an icon.
</P>

<H4>
B.4.24. require_vendor
</H4>

<P>Default value: 0
</P>

<P>The require_vendor entry is used to direct RPM to require that every package built must
contain vendor information. The default value directs RPM to not enforce this requirement.
If the entry has a non-zero value, RPM will only build packages that define a vendor.
</P>

<H4>
B.4.25. rpmdir
</H4>

<P>Default value: (topdir)/RPMS
</P>

<P>The rpmdir entry is used to define the path to the directory in which RPM will write
binary package files. Its default value is taken from the value of the
topdir entry, with /RPMS appended to it. Note that if you redefine
rpmdir, you'll need to specify a complete path. RPM will
automatically add an architecture-specific directory to the end of the path. For example, on an
Intel-based system, the actual path would be
</P>
<!-- CODE SNIP //-->
<PRE>
/usr/src/redhat/RPMS/i386
</PRE>
<!-- END CODE SNIP //-->

<A NAME="PAGENUM-365"><P>Page 365</P></A>

<H4>
B.4.26. signature
</H4>

<P>Default value: (none)
</P>

<P>The signature entry is used to define the type of signature that is to be added to each
package built. At the present time, only signatures from PGP are supported. Therefore, the only
acceptable value is pgp.
</P>

<P>For more information on signing packages with PGP, see Chapter 17.
</P>

<H4>
B.4.27. sourcedir
</H4>

<P>Default value: (topdir)/SOURCES
</P>

<P>The sourcedir entry is used to define the path to the directory in which RPM will look
for sources. Its default value is taken from the value of the
topdir entry, with /SOURCES appended to it. Note that if you redefine
sourcedir, you'll need to specify a complete path.
</P>

<H4>
B.4.28. specdir
</H4>

<P>Default value: (topdir)/SPECS
</P>

<P>The specdir entry is used to define the path to the directory in which RPM will look for
spec files. Its default value is taken from the value of the
topdir entry, with /SPECS appended to it. Note that if you redefine
specdir, you'll need to specify a complete path.
</P>

<H4>
B.4.29. srcrpmdir
</H4>

<P>Default value: (topdir)/SRPMS
</P>

<P>The srcrpmdir entry is used to define the path to the directory in which RPM will write
source package files. Its default value is taken from the value of the
topdir entry, with /SRPMS appended to it. Note that if you redefine
srcrpmdir, you'll need to specify a complete path.
</P>

<H4>
B.4.30. timecheck
</H4>

<P>Default value: (none)
</P>

<P>The timecheck entry is used to define the default number of seconds to apply to the
--timecheck option when building packages. For more information on the
--timecheck option, please see Chapter 12, &quot;rpm
-b Command Reference.&quot;
</P>

<H4>
B.4.31. tmppath
</H4>

<P>Default value: /var/tmp
</P>

<A NAME="PAGENUM-366"><P>Page 366</P></A>



<P>The tmpdir entry is used to define a path to the directory that RPM will use for
temporary work space. This normally consists of temporary scripts that are used during the build
process. It should be set to an absolute path (that is, starting with
/).
</P>

<H4>
B.4.32. topdir
</H4>

<P>Default value: /usr/src/redhat
</P>

<P>The topdir entry is used to define the path to the
top-level directory in RPM's build directory tree. It should be set to an absolute path (that is, starting with
/). The following entries base their default values on the value of
topdir:
</P>

<UL>
<LI>          builddir
<LI>          rpmdir
<LI>          sourcedir
<LI>          specdir
<LI>          srcrpmdir
</UL>

<H4>
B.4.33. vendor
</H4>

<P>Default value: (none)
</P>

<P>The vendor entry is used to define the name of the organization that is responsible for
distributing the packaged software. Normally, this would be the name of a business or other
such entity.
</P>
<BR><BR>


<P><CENTER>
<a href="appendix-a.html">Previous</a> | <a href="ewtoc.html">Table of Contents</a> | <a href="appendix-c.html">Next</a></CENTER></P>



</td>
</tr>
</table>
<!-- begin footer information -->



</body></html>