lcfg-rpmcache - The LCFG component to maintain a local RPM cache
This component maintains a cache directory on the local machine containing a copy of every RPM specified in an rpmcfg file. The list of available RPMs is obtained by reading a file called rpmlist from the server in exactly the same way as updaterpms. Wildcards in the rpmcfg file are evaluated, and the cache is updated by fetching RPMs from the repository over HTTP. Normally, the rpmcfg file will be the client's own rpmcfg file so that the cache contains a copy of every RPM that should be installed on the system. The updaterpms component may then use the cache as the source directory, allowing the system to be updated without direct access to a remote repository.
The run method is used to initiate a cache update and supports the following options:
Force old entries to be removed (cleaned) from the cache, even if the preserve resource is set.
Do not delete (preserve) old entries in the cache, even if the preserve resource is not set.
root is prefixed to the cachedir resource to form the name of the cache directory. This is useful at install time.
Test only. Display cache operations that would be performed without performing them.
The install method is identical to the run method, except that the resources are loaded directly from the profile (rather than the status file), and no locking or status saving takes place. This is intended for use at install time (only).
The pathname of the cache directory on the client.
Additional options to be passed to cpp when reading rpmcfg files.
If this resource is set, then the genhdfile program is run on rpms after downloading them, to create the header info file.
A (space-separated) list of directories on the client machine to be treated as local master repositories. Any RPMs present in these directories will not be searched for on the server, and will not be copied into the cache.
Do not delete old entries from the cache.
The name of a file to be created in the cache directory, containing a list of the RPMs in the cache. By default, this is null and no file is created.
A comma separated list of URLs for directories containing RPMs. Each directory should contain a set of RPMs, and a file named rpmlist, listing the available RPMs. Local directory names may also be specified instead of URLs.
The full pathname of the rmcfg file on the client machine containing the list of RPMs to maintain in the cache. Multiple (comma-separated) rpmcfg files may be specified, in which case they are effectively concatenated. rpmcfg files may also be specified as remote URLs which are automatically downloaded - however, note that any files included with #include will not be automatically downloaded.
The name of a lock file in the cache. This file will be removed before a cache update, and created after the update. This prevents updaterpms from atempting to run during a cache update.
A command run run after a sucessful update of the cache. For example (and by default) om updaterpms run.
Solaris9, Fedora3, Fedora5, Fedora6, Scientific5
Paul Anderson <dcspaul@inf.ed.ac.uk>