NAME
rpmcache - 缓存 RPM 打包头部
SYNOPSIS
rpmcache [ PACKAGE_NAME ... ]
DESCRIPTION
rpmcache 遍历文件树，可能通过 FTP 使用远程文件，使用 glob(7) 表达式过滤路径，读取 rpm 打包头部。最新的软件包 (对于相同的软件包名称，比较代/版本/发行数字，以及构建时间，来解决冲突) 的头部，如果唯一的话，就缓存在 rpm 数据库中。rpm 数据库缓存可以用来提供解决软件包未知依赖关系时的建议。
没有特定于 rpmcache 的选项，只有一般的 rpm 选项。参见 rpmcache 用法信息，察看当前已实现的内容。
要搜索的文件树路径是以 rpm 宏配置的。最终路径是 5 个独立的元素的拼装。下面是用于配置 rpmcache 的宏名称。在文件树中将遍历：
- %_bhpath
- "路径" 一级包含要遍历的文件树的文件树路径 (或 URL) 的前缀部分。这里不能使用 glob(7) 表达式。
- %_bhcoll
- "集合" 一级包含一个字符串 (或 glob(7) 表达式)，来匹配 %_bhpath 的子目录。
- %_bhN
- "名称" 一级包含一个字符串 (或 glob(7) 表达式)，来匹配 %_bhcoll 的子目录。可以用 PACKAGE_NAME 参数来构造一个 glob(7) 表达式，匹配 Redhat 构建系统中任何指定软件包的名称，在 Redhat 之外几乎没有任何用处。
- %_bhVR
- "版本发行" 一级包含一个字符串 (或 glob(7) 表达式)，来匹配 %_bhN 的子目录。
- %_bhA
- "体系结构" 一级包含一个字符串 (或 glob(7) 表达式)，来匹配 %_bhVR 的子目录。
缓存数据库的位置也使用一个 rpm 宏
- %_cache_dbpath
- 来配置。默认的值是 /var/spool/up2date/cache。
缓存数据库与 rpm 数据库的格式完全相同，可以用在 rpm 命令中。例如，要使用缓存数据库，来提供建议，给出满足软件包安装时依赖关系的软件包，可以将下面的宏配置在 /etc/rpm/macros 或 ~/.rpmmacros 中：
- %_solve_dbpath
- 用于提供依赖关系建议的数据库的位置
范例 (最小) 配置，针对一个 Redhat 文件树：
%_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)
范例 (最小) 配置，针对一个 Redhat FTP 树：
%_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. 请将有关 rpm-devel 软件包的错误报告和特性需求提交到 bugzilla： http://bugzilla.redhat.com/ <URL:http://bugzilla.redhat.com/>
SEE ALSO
rpm(8), glob(7),
#p#
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 concatenation 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 configured 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.redhat.com/>
SEE ALSO
rpm(8), glob(7),
