1RPMCACHE(8) Red Hat Linux RPMCACHE(8)
2
6 rpmcache - Cache RPM Package Headers
7
9 rpmcache [ PACKAGE_NAME ... ]
10
13 rpmcache walks a file tree, possibly remotely using FTP, filtering
14 paths using glob(7) expressions, reading rpm package headers. The lat‐
15 est (i.e. comparing package epoch/version/release for identical package
16 names and using the build time as a tie breaker) package headers, if
17 they are unique, are cached in an rpm database. The rpm database cache
18 can be used to provide suggested paths to packages that resolve unknown
19 dependencies.
20 There are no rpmcache specific options, only common rpm options. See
22 the rpmcache usage message for what is currently implemented.
23 The file tree path to be searched is configured using rpm macros. The
25 final path is the concatenation of 5 individual elements. Here are the
26 macro names used to configure rpmcache, in the same order that they
27 will be concatenated to build the file tree path that will be walked:
28 %_bhpath
30 The "path" level contains the leading part of the file tree path
31 (or URL) for the file tree to be walked. No glob(7) expres‐
32 sions, here, please.
33 %_bhcoll
35 The "collection" level contains a string (or glob(7) expression)
36 to match sub-directories of %_bhpath.
37 %_bhN The "name" level contains a string (or glob(7) expression) to
39 match sub-directories of %_bhcoll. The PACKAGE_NAME arguments
40 are used to construct a glob(7) expression that will match any
41 of specific package names within the Red Hat build system, and
42 are almost certainly not of use to anyone outside of Red Hat.
43 %_bhVR The "version-release" level contains a string (or glob(7)
45 expression) to match sub-directories of %_bhN.
46 %_bhA The "arch" level contains a string (or glob(7) expression) to
48 match sub-directories of %_bhVR.
49 The location of the cache database is also configured using an rpm
51 macro:
52 %_cache_dbpath
54 The location of the cache database. The default value is
55 /var/spool/up2date/cache.
56 The cache database is identical in format to an rpm database, and can
58 be used with rpm from the command line. For example, to use the cache
59 database to provide suggestions for packages that provide dependencies
60 needed by a package install, the following macro should be configured
61 in either /etc/rpm/macros or ~/.rpmmacros:
62 %_solve_dbpath
64 The location of the database that is used to provide suggested
65 dependency resolutions.
66 Example (minimal) configuration for a Red Hat beehive tree:
68 %_cache_dbpath /var/spool/up2date/cache
69 %_solve_dbpath %{_cache_dbpath}
70 %_bhpath file://localhost/mnt/redhat/beehive/comps/dist
71 %_bhcoll 7.3
72 %_bhN @(basesystem|bash|filesystem|glibc-common|glibc|ldconfig|libtermcap|mktemp|setup|termcap)
73 %_bhVR *
74 %_bhA @(i[3456]86|noarch)
75 Example (minimal) configuration for a Red Hat FTP tree:
77 %_cache_dbpath /var/spool/up2date/cache
78 %_solve_dbpath %{_cache_dbpath}
79 %_bhpath ftp://localhost/mnt/dist
80 %_bhcoll @(7.3|7.2|7.1|7.0|6.2|6.1|6.0|5.2|5.1|5.0)
81 %_bhN @(%{_arch})
82 %_bhVR *
83 %_bhA @(i[3456]86|noarch)
84
86 Yup. Please file bug reports and RFE's against the rpm-devel package
87 using bugzilla: http://bugzilla.redhat.com/ <URL:http://bugzilla.red‐
88 hat.com/>
89
91 rpm(8), glob(7),
92 http://www.rpm.org/ <URL:http://www.rpm.org/>
94
96 Jeff Johnson <jbj@redhat.com>
97Red Hat, Inc. 05 July 2002 RPMCACHE(8)