From 30d565162af0ce5472294fd1ef1b9d076d53336f Mon Sep 17 00:00:00 2001 From: Fabio Erculiani Date: Tue, 22 Nov 2011 22:07:14 +0100 Subject: [PATCH] [sci-astronomy] new particle --- weekly/sci-astronomy.particle | 96 +++++++++++++++++++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 weekly/sci-astronomy.particle diff --git a/weekly/sci-astronomy.particle b/weekly/sci-astronomy.particle new file mode 100644 index 0000000..699dd22 --- /dev/null +++ b/weekly/sci-astronomy.particle @@ -0,0 +1,96 @@ +# 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: + sci-astronomy/cdsclient, + sci-astronomy/celestia, + sci-astronomy/ds9-bin, + sci-astronomy/funtools, + sci-astronomy/galaxy, + sci-astronomy/gasgano, + sci-astronomy/kapteyn, + sci-astronomy/orsa, + sci-astronomy/pyephem, + sci-astronomy/scamp, + sci-astronomy/sextractor, + sci-astronomy/skycat, + sci-astronomy/stellarium, + sci-astronomy/stiff, + sci-astronomy/swarp, + sci-astronomy/wcslib, + sci-astronomy/wcstools, + sci-astronomy/xephem, + sci-astronomy/xfitsview + +# 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