can fill up a chroot directory for ports
building usage. It will perform a set of actions
that should fill up a destination chroot
directory from the base system (or an optional
As far as possible, proot
will create hardlinks
instead of copying files, so that cloning an existing chroot will often only
Some attributes can take multiple values. As a shorthand, several values can be
specified in a row without having to repeat the
name, for instance:
proot -B /build actions=unpopulate_light
mostly contains one
assignment per line, with comments starting with a ‘#’
(in the order of execution) are as
By default, proot
won't be run. It will also run
if a snapshot location is provided, or
Add actions with
remove them with
Other attributes are:
The following entries won't be erased during a
- Items explicitly marked with the
- A snapshot directory
containing the base sets.
- All the ports specific sub directories if they are
defined, namely DISTDIR,
WRKOBJDIR, LOGDIR, PACKAGE_REPOSITORY,
- The PORTSDIR itself, unless
copy_ports is used.
- Any mountpoint.
- Data explicitly copied through other actions, e.g.,
extra files, key files...
The following configfile
sets things up for an
initial build on a dpb(1)
It assumes /build/data
is a separate partition that
won't be cleaned up by unpopulate_light
, and that
can be mounted on slaves. Note also that /tmp
should be a fast local directory on every machine of the cluster.
is a startup script for
Initial invocation on the master could be
to ensure correct permissions for existing data under various ports directories.
Slaves should not need the extra arguments, as the directories will already have