particles/weekly/app-doc.particle
2012-07-04 07:50:02 +00:00

114 lines
3.1 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-doc/NaturalDocs,
app-doc/abs-guide,
app-doc/autobook,
app-doc/blas-docs,
app-doc/casting-spels-emacs,
app-doc/djbdns-man,
app-doc/doxygen,
app-doc/ebookmerge,
app-doc/edox-data,
app-doc/elisp-manual,
app-doc/gimp-help,
app-doc/gnucash-docs,
app-doc/halibut,
app-doc/jargon,
app-doc/lapack-docs,
app-doc/linkers-and-loaders,
app-doc/linux-device-drivers,
app-doc/linux-gazette-base,
app-doc/linux-gazette-all,
app-doc/linux-kernel-in-a-nutshell,
app-doc/linuxfromscratch,
app-doc/mkdoxy,
app-doc/openmotif-manual,
app-doc/php-docs,
app-doc/phrack-all,
app-doc/pms,
app-doc/podbrowser,
app-doc/psmark,
app-doc/root-docs,
app-doc/selfhtml,
app-doc/selflinux,
app-doc/single-unix-specification,
app-doc/tldp-howto,
app-doc/vilearn,
app-doc/xmltoman,
app-doc/zsh-lovers
# Entropy repository where to commit packages
# Mandatory, cannot be empty
repository: sabayon-hell
# Allow Source Package Manager (Portage) repository change?
# Valid values are either "yes" or "no"
# Default is: no
spm-repository-change: no
# Allow compiling package even if it's not actually installed on system?
# Valid values are either "yes" or "no"
# Default is: no
not-installed: no
# 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: no
# Allow package rebuild?
# Valid values are either "yes" or "no"
# Default is: no
rebuild: no
# 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: yes
# Allow removed USE flags?
# Valid values are either "yes" or "no"
# Default is: no
removed-useflags: yes
# Package pre execution script hook
# Valid value is path to executable file
# Env vars:
# BUILDER_PACKAGE_NAME = name of the package 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:
# BUILDER_PACKAGE_NAME = name of the package that would be built
# pkgpost: /home/fabio/repos/entropy/services/matter_examples/pkgpost.sh
# Env vars:
# MATTER_PACKAGE_NAME = name of the package that would be built. It does
# not reflect the name of the failing package, because it could be just a
# dependency of it.
# 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: /particles/hooks/buildfail.sh
# For more info regarding exported environment variables, please see:
# matter --help