NAME

lcfg-mock - An LCFG component to manage the mock build tool

DESCRIPTION

Mock is a simple program that will build source RPMs inside a chroot. It does not do anything terribly fancy other than populate a chroot with the contents specified by a configuration file, then build any input SRPM(s) in that chroot.

This is an LCFG component to manage the configuration files for the mock build tool. That is, it configures some options in /etc/mock/site-defaults.cfg and the specific configuration file for each chroot. It does not attempt to manage all possible options, just those which are most likely to need modification. If you have any more options which require configuration get in touch with the component author.

RESOURCES

basedir

This is the directory where mock creates the chroots. You will want this to somewhere with a reasonable amount of free disk space. It defaults to /var/lib/mock.

cache_topdir

This is the directory where mock caches packages pulled in with yum and also the gzipped tar file for each chroot. Again, this should be located somwhere with a good amount of free disk space. It defaults to being <%mock.basedir%>/cache

rpmbuild_timeout

This is an integer representing the maximum amount of time which rpmbuild should be allowed to run. This provides the ability to kill runaway builds. If set to zero then no timeout will be applied. The default value is 0.

buildgroup

Any user wanting to use mock to do builds must be a member of this group. By default this is mock.

pkgsrc

This is a URL representing the base of the main package repository which yum will use to acquire build requirements. You do not need to use this option, you can set a specific baseurl for any or all repositories in the yum configuration. For example, you could set it to http://www.example.org/rpms/. The base URL for a repository will be built from this like $pkgsrc/$release/$releasever/$basearch/$repo/

chroots

This is a list of tags representing the chroots you want to be configured

chrtname_chroot

The name for the chroot, you only need to set this if you want characters (such as hyphen) in the name which are not valid LCFG tag names. If it is not set the tag name is used. This is the name which users will use to identify the target chroot through the -r option for mock.

basearch_chroot

The base architecture for the chroot (e.g. i386 or x86_64).

dist_chroot

The mock dist configuration option, only useful for --resultdir variable substitution.

release_chroot

The name for the release, e.g. fedora or scientific. Used when building the baseurl yum option for the repository if no baseurl is specified.

releasever_chroot

The version number for the release, e.g. 5 or 6. Used when building the baseurl yum option for the repository if no baseurl is specified.

repos_chroot

A list of yum repositories for this chroot.

baseurl_chroot_repo

A specific baseurl yum setting for this repository.

exclude_chroot_repo

A space-separated list of yum exclusions, useful for preventing packages being pulled in from the wrong repository.

PLATFORMS

Scientific5

AUTHOR

Stephen Quinney <squinney@inf.ed.ac.uk>