particles/daily/sys-kernel.particle

# 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:
	sys-kernel/buffalo_kb_pro-sources,
	sys-kernel/buffalo_ls_chl-sources,
	sys-kernel/buffalo_ls_chl2-sources,
	sys-kernel/buffalo_ls_hgl-sources,
	sys-kernel/buffalo_ls_mini-sources,
	sys-kernel/buffalo_ls_pro_duo_rev1-sources,
	sys-kernel/buffalo_ls_pro_duo_rev2-sources,
	sys-kernel/buffalo_ls_pro_live-sources,
	sys-kernel/buffalo_ls_ql-sources,
	sys-kernel/buffalo_ls_vl-sources,
	sys-kernel/buffalo_ls_wvl-sources,
	sys-kernel/buffalo_ls_xhl-sources,
	sys-kernel/genkernel,
	sys-kernel/go-sources,
	sys-kernel/linux-buffalo_kb_pro,
	sys-kernel/linux-buffalo_ls_chl2,
	sys-kernel/linux-buffalo_ls_chl,
	sys-kernel/linux-buffalo_ls_hgl,
	sys-kernel/linux-buffalo_ls_mini,
	sys-kernel/linux-buffalo_ls_pro_duo_rev1,
	sys-kernel/linux-buffalo_ls_pro_duo_rev2,
	sys-kernel/linux-buffalo_ls_pro_live,
	sys-kernel/linux-buffalo_ls_ql,
	sys-kernel/linux-buffalo_ls_vl,
	sys-kernel/linux-buffalo_ls_wvl,
	sys-kernel/linux-buffalo_ls_xhl

# Entropy repository where to commit packages
# Mandatory, cannot be empty
repository: sablink.nas-central.org

# 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: 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