rpmcache(8) [redhat man page]

RPMCACHE(8)							   Red Hat Linux						       RPMCACHE(8)

NAME

       rpmcache - Cache RPM Package Headers

SYNOPSIS

       rpmcache [ PACKAGE_NAME ... ]

DESCRIPTION

       rpmcache walks a file tree, possibly remotely using FTP, filtering paths using glob(7) expressions, reading rpm package headers. The latest
       (i.e. comparing package epoch/version/release for identical package names and using the build time as a tie breaker)  package  headers,	if
       they  are  unique,  are	cached in an rpm database.  The rpm database cache can be used to provide suggested paths to packages that resolve
       unknown dependencies.

       There are no rpmcache specific options, only common rpm options.  See the rpmcache usage message for what is currently implemented.

       The file tree path to be searched is configured using rpm macros. The final path is the concatentaion of 5 individual  elements.  Here  are
       the  macro  names  used	to  configure  rpmcache, in the same order that they will be concatenated to build the file tree path that will be
       walked:

       %_bhpath
	      The "path" level contains the leading part of the file tree path (or URL) for the file tree to be walked.  No  glob(7)  expressions,
	      here, please.

       %_bhcoll
	      The "collection" level contains a string (or glob(7) expression) to match sub-directories of %_bhpath.

       %_bhN  The  "name"  level  contains  a string (or glob(7) expression) to match sub-directories of %_bhcoll.  The PACKAGE_NAME arguments are
	      used to construct a glob(7) expression that will match any of specific package names within the Red Hat build system, and are almost
	      certainly not of use to anyone outside of Red Hat.

       %_bhVR The "version-release" level contains a string (or glob(7) expression) to match sub-directories of %_bhN.

       %_bhA  The "arch" level contains a string (or glob(7) expression) to match sub-directories of %_bhVR.

       The location of the cache database is also configured using an rpm macro:

       %_cache_dbpath
	      The location of the cache database. The default value is /var/spool/up2date/cache.

       The cache database is identical in format to an rpm database, and can be used with rpm from the command line. For example, to use the cache
       database to provide suggestions for packages that provide dependencies needed by a package install, the following macro should  be  config-
       ured in either /etc/rpm/macros or ~/.rpmmacros:

       %_solve_dbpath
	      The location of the database that is used to provide suggested dependency resolutions.

   Example (minimal) configuration for a Red Hat beehive tree:
       %_cache_dbpath  /var/spool/up2date/cache
       %_solve_dbpath  %{_cache_dbpath}
       %_bhpath        file://localhost/mnt/redhat/beehive/comps/dist
       %_bhcoll        7.3
       %_bhN	       @(basesystem|bash|filesystem|glibc-common|glibc|ldconfig|libtermcap|mktemp|setup|termcap)
       %_bhVR	       *
       %_bhA	       @(i[3456]86|noarch)

   Example (minimal) configuration for a Red Hat FTP tree:
       %_cache_dbpath  /var/spool/up2date/cache
       %_solve_dbpath  %{_cache_dbpath}
       %_bhpath        ftp://localhost/mnt/dist
       %_bhcoll        @(7.3|7.2|7.1|7.0|6.2|6.1|6.0|5.2|5.1|5.0)
       %_bhN	       @(%{_arch})
       %_bhVR	       *
       %_bhA	       @(i[3456]86|noarch)

BUGS

       Yup.  Please file bug reports and RFE's against the rpm-devel package using bugzilla: http://bugzilla.redhat.com/ <URL:http://bugzilla.red-
       hat.com/>

SEE ALSO

       rpm(8), glob(7),

	http://www.rpm.org/ <URL:http://www.rpm.org/>

AUTHORS

       Jeff Johnson <jbj@redhat.com>

Red Hat, Inc.							   05 July 2002 						       RPMCACHE(8)

Check Out this Related Man Page

RPMKEYS(8)						      System Manager's Manual							RPMKEYS(8)

NAME

       rpmkeys - RPM Keyring

SYNOPSIS

       rpmkeys {--import|--checksig}

DESCRIPTION

       The general forms of rpm digital signature commands are

       rpmkeys --import PUBKEY ...

       rpmkeys {-K|--checksig} PACKAGE_FILE ...

       The  --checksig	option	checks all the digests and signatures contained in PACKAGE_FILE to ensure the integrity and origin of the package.
       Note that signatures are now verified whenever a package is read, and --checksig is useful to verify all  of  the  digests  and	signatures
       associated with a package.

       Digital	signatures  cannot be verified without a public key.  An ASCII armored public key can be added to the rpm database using --import.
       An imported public key is carried in a header, and key ring management is performed exactly like package management. For example, all  cur-
       rently imported public keys can be displayed by:

       rpm -qa gpg-pubkey*

       Details about a specific public key, when imported, can be displayed by querying.  Here's information about the Red Hat GPG/DSA key:

       rpm -qi gpg-pubkey-db42a60e

       Finally, public keys can be erased after importing just like packages. Here's how to remove the Red Hat GPG/DSA key

       rpm -e gpg-pubkey-db42a60e

SEE ALSO

       popt(3),
       rpm(8),
       rpmdb(8),
       rpmsign(8),
       rpm2cpio(8),
       rpmbuild(8),
       rpmspec(8),

       rpmkeys	--help - as rpm supports customizing the options via popt aliases it's impossible to guarantee that what's described in the manual
       matches what's available.

       http://www.rpm.org/ <URL:http://www.rpm.org/>

AUTHORS

       Marc Ewing <marc@redhat.com>
       Jeff Johnson <jbj@redhat.com>
       Erik Troan <ewt@redhat.com>
       Panu Matilainen <pmatilai@redhat.com>

Red Hat, Inc							  29 October 2010							RPMKEYS(8)

Linux and UNIX Man Pages

rpmcache(8) [redhat man page]

Check Out this Related Man Page