79c63fef14
Previously, each package in the particle was analyzed on its own and spawning portage against multiple packages was not possible. This commit introduces the ability to aggregate packages in particles in "groups", so that they can be considered together in the same portage merge transaction. The previously exported environment variable MATTER_PACKAGE_NAME has been renamed into MATTER_PACKAGE_NAMES and contains a space separated list of package dependencies that are in the merge transaction.
83 lines
2.8 KiB
Plaintext
83 lines
2.8 KiB
Plaintext
# Entropy Matter, Automated Entropy Packages Build Service, example spec file
|
|
|
|
# List of packages required to be built.
|
|
# Comma separated, example: app-foo/bar, bar-baz/foo
|
|
# Mandatory, cannot be empty
|
|
packages: =app-misc/entrofoo-3
|
|
|
|
# Entropy repository where to commit packages
|
|
# Mandatory, cannot be empty
|
|
repository: community0
|
|
|
|
# Allow Source Package Manager (Portage) repository change?
|
|
# Valid values are either "yes" or "no"
|
|
# Default is: no
|
|
spm-repository-change: yes
|
|
|
|
# Allow compiling package even if it's not actually installed on system?
|
|
# Valid values are either "yes" or "no"
|
|
# Default is: no
|
|
not-installed: yes
|
|
|
|
# Allow dependencies to be pulled in?
|
|
# Valid values are either "yes" or "no"
|
|
# Default is: no
|
|
dependencies: yes
|
|
|
|
# Allow package downgrade?
|
|
# Valid values are either "yes" or "no"
|
|
# Default is: no
|
|
downgrade: yes
|
|
|
|
# Allow package rebuild?
|
|
# Valid values are either "yes" or "no"
|
|
# Default is: no
|
|
rebuild: yes
|
|
|
|
# Make possible to continue if one or more packages fail to build?
|
|
# Valid values are either "yes" or "no"
|
|
# Default is: no
|
|
keep-going: yes
|
|
|
|
# Allow new USE flags?
|
|
# Valid values are either "yes" or "no"
|
|
# Default is: no
|
|
new-useflags: no
|
|
|
|
# Allow removed USE flags?
|
|
# Valid values are either "yes" or "no"
|
|
# Default is: no
|
|
removed-useflags: yes
|
|
|
|
# Package pre execution script hook, executed for each package
|
|
# Valid value is path to executable file
|
|
# Env vars:
|
|
# MATTER_PACKAGE_NAMES = list of package names that would be built
|
|
# pkgpre: /home/fabio/repos/entropy/services/matter_examples/pkgpre.sh
|
|
|
|
# Package build post execution script hook, executed for each package
|
|
# Valid value is path to executable file
|
|
# Env vars:
|
|
# MATTER_PACKAGE_NAMES = list of package names that would be built
|
|
# To the pkgpost hook, is given one argv parameter, corresponding to the
|
|
# build exit status, which is 0 for no issues, != 0 for issue.
|
|
# If pkgpost hook returns != 0 exit status, this will replace the exit status
|
|
# of the build procedure, which gets returned by build caller (so you have a
|
|
# good change of making the whole matter execution abort).
|
|
# pkgpost: /home/fabio/repos/entropy/services/matter_examples/pkgpost.sh
|
|
|
|
# Env vars:
|
|
# MATTER_PACKAGE_NAMES = list of package names that would be built. It
|
|
# does not reflect the name of the failing packages, because they could be
|
|
# just dependencies.
|
|
# MATTER_PORTAGE_FAILED_PACKAGE_NAME = exact name (atom, CPV) of the failing
|
|
# package, the one that triggered the buildfail hook.
|
|
# MATTER_PORTAGE_REPOSITORY = Portage repository from where the package
|
|
# comes from
|
|
# MATTER_PORTAGE_BUILD_LOG_DIR = directory containing all the build logs of
|
|
# the failed package
|
|
buildfail: /home/fabio/repos/entropy/services/matter_examples/buildfail-tinderbox.sh
|
|
|
|
# For more info regarding exported environment variables, please see:
|
|
# matter --help
|