/etc/buildspaces

Description

The buildspaces configuration file, usually located at /etc/buildspaces, contains configuration information relating to the collection of build-spaces which are installed and managed on this build-server. Configuration information for the individual build-spaces is contained inside the build-space directory tree at etc/buildspace.

Example

# Path to the directory containing the build-spaces
BUILDSPACEROOT="/mnt/buildspaces"

# List of build-spaces on the same architecture as the host
BUILDSPACESXX="x86-64bit-server x86-64bit-workstation"

# List of build-spaces requiring linux32 to be executed prior to chroot
BUILDSPACES32="x86-32bit-server x86-32bit-workstation"

# Path to the directory containing the repositories
REPOSROOT="/mnt/repositories"

# Gentoo rsync location and options
GENTOORSYNC="rsync.gentoo.org::gentoo-portage"
GENTOORSOPT="--archive --delete --quiet --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"

# Should we run layman --sync-all when synchronising the live repository
AUTOLAYMANSYNC="no"

# Should we run auto-patch --sync when synchronising the live repository
# and if so which options we should pass
AUTOPATCHSYNC="no"
AUTOPATCHSYNCOPTS="--quiet --sync"

# Repository rsync options
REPORSOPT="--quiet --archive --no-D --delete-during"

# Should we run auto-patch when synchronising a testing repository
# and if so which options we should pass
AUTOPATCHTEST="no"
AUTOPATCHTESTOPTS="--quiet --copy-files --apply-patches"

# Should we run rebuild-portage-caches inside the build-space when
# synchronising a testing repository.
AUTOREBUILD="yes"

BUILDSPACEROOT

The BUILDSPACEROOT variable should be set to the location of the root path of the build-spaces. All build-spaces should be subdirectories of this path and the name of the build-space directory should equal the name of the build-space in the lists below.

BUILDSPACESXX

This variable should contain a space separated list of the names of the build-spaces which are on the same architecture as the build-server. If a 32bit build-server is being configured then all build-spaces should be listed here. If a 64bit build-server is being configured then only the 64bit build-spaces should be listed here.

BUILDSPACES32

This variable should contain a space separated list of the names of the build-spaces which require the linux32 application to be used to start the chroot into the build-space. If a 32bit build-server is being configured then no build-spaces should be listed here. If a 64bit build-server is being configured then only the 32bit build-spaces should be listed here.

REPOSROOT

The BUILDSPACEROOT variable should be set to the location of the root path of the repositories. The "live", testing and stable repositories will be subdirectories of this location named live, testing and stable accordingly. The testing and stable directories will contain subdirectories for each configured build-space name each containing a portage snapshot, a snapshot of any overlays, a copy of the configuration used for the build-space, kernel images and binary packages.

GENTOORSYNC

This variable contains the location of the Gentoo rsync server with which the "live" repository should be synchronised. The default value will use any of the available rsync mirrors and should not usually be modified unless your organisation maintains a local mirror of the portage tree.

GENTOORSOPT

This variable contains the options which will be passed to the rsync application when synchronising with the Gentoo portage mirrors. The default options are the same as the default options used by portage and should not need to be modified.

AUTOLAYMANSYNC

When synchronising the "live" repository the layman utility will be invoked with the --sync-all option if this variable is set to "yes".

AUTOPATCHSYNC

When synchronising the "live" repository the auto-patch-portage utility will be invoked if this variable is set to "yes". For more information see the documentation for the auto-patch-portage utility.

AUTOPATCHSYNCOPTS

When using the auto-patch-portage utility these options will be used. Again, more information is available in the documentation for the auto-patch-portage utility.

REPORSOPT

The REPORSOPT variable allows the options used by the rsync application when synchronising the testing or stable repositories to be configured. The default options should suffice for most installations.

AUTOPATCHTEST

If this variable is set to "yes" then the auto-patch-portage utility will be invoked on the testing repository automatically after every synchronisation with the "live" repository. For more information see the documentation for the auto-patch-portage utility.

AUTOPATCHTESTOPTS

When invoking the auto-patch-portage utility these options will be used. More information is available in the documentation for the auto-patch-portage utility.

AUTOREBUILD

If this variable is set to "yes" then the rebuild-portage-caches utility will be executed inside each build-space automatically after every synchronisation of the related testing repository.