[gnome-base] new particle

This commit is contained in:
Fabio Erculiani 2011-11-12 23:57:38 +01:00
parent 23735e5607
commit 44a82ad98f

117
weekly/gnome-base.particle Normal file
View File

@ -0,0 +1,117 @@
# 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:
gnome-base/dconf,
gnome-base/gconf,
gnome-base/gdm,
gnome-base/gnome,
gnome-base/gnome-applets,
gnome-base/gnome-common,
gnome-base/gnome-control-center,
gnome-base/gnome-core-apps,
gnome-base/gnome-core-libs,
gnome-base/gnome-desktop,
gnome-base/gnome-desktop,
gnome-base/gnome-extra-apps,
gnome-base/gnome-fallback,
gnome-base/gnome-js-common,
gnome-base/gnome-keyring,
gnome-base/gnome-menus,
gnome-base/gnome-menus,
gnome-base/gnome-mime-data,
gnome-base/gnome-panel,
gnome-base/gnome-session,
gnome-base/gnome-settings-daemon,
gnome-base/gnome-shell,
gnome-base/gnome-vfs,
gnome-base/gsettings-desktop-schemas,
gnome-base/gvfs,
gnome-base/libbonobo,
gnome-base/libbonoboui,
gnome-base/libglade,
gnome-base/libgnome,
gnome-base/libgnome-keyring,
gnome-base/libgnomecanvas,
gnome-base/libgnomekbd,
gnome-base/libgnomeprint,
gnome-base/libgnomeprintui,
gnome-base/libgnomeui,
gnome-base/libgtop,
gnome-base/librsvg,
gnome-base/libslab,
gnome-base/nautilus,
gnome-base/orbit
# 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