The following sections contain the available handler classes that can be
used for the class option in
sets.conf, together with a description about required
and optional configuration options for single and multi set configurations.
Note that not all classes support both configuration styles.
This class implements a simple file based package set. All atoms from
configured file are used to form the set, and currently only simple and
versioned atoms are supported (no use conditionals or any-of constructs).
For descriptive purposes the file can be accompanied by a file with the
same name plus a .metadata suffix which can contain
metadata sections for description, author, location and so on. Each section
has the form key: value where value
can contain multiple lines. Therefore sections have to be separated by
blank lines. For example:
description: This is a somewhat longer description than usual. So it needs more than one line. homepage: https://www.foobar.org/ author: John Doe <john@doe.com>
In a single set configuration this class supports the following options:
filename: Required. Specifies the path to the file
that should be used for the package set.
greedy: Optional, defaults to false.
Determines if atoms in the package should include all installed slots (when set to
true) or if no slot expansion is wanted (when set to
false). This option only affects packages that have multiple
slots available (e.g. sys-kernel/gentoo-sources).
In a multi set configuration this class supports the following options:
directory: Optional, defaults to
/etc/portage/sets. Specifies the path to a directory
containing package set files. For each file (excluding metadata files) in
that location a separate package set is created.
name_pattern: Optional, defaults to
$name. This describes the naming pattern
to be used for creating the sets. It must contain either
$name or ${name}, which
will be replaced by the filename (without any directory components).