particles/weekly/mail-filter.particle
2012-02-10 13:46:15 +00:00

123 lines
3.7 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:
mail-filter/anomy-sanitizer,
mail-filter/ask,
mail-filter/assp,
mail-filter/bmf,
mail-filter/bogofilter,
mail-filter/clamassassin,
mail-filter/clamsmtp,
mail-filter/dcc,
mail-filter/dk-milter,
mail-filter/dkim-milter,
mail-filter/dovecot-antispam,
mail-filter/dspam,
mail-filter/gld,
mail-filter/imapfilter,
mail-filter/isbg,
mail-filter/libmilter,
mail-filter/libsieve,
mail-filter/libspf2,
mail-filter/maildrop,
mail-filter/mailfilter,
mail-filter/mapson,
mail-filter/milter-regex,
mail-filter/mimedefang,
mail-filter/normalizemime,
mail-filter/opendkim,
mail-filter/p3scan,
mail-filter/policyd,
mail-filter/popfile,
mail-filter/postgrey,
mail-filter/procmail,
mail-filter/procmail-lib,
mail-filter/pypolicyd-spf,
mail-filter/razor,
mail-filter/rblcheck,
mail-filter/sid-milter,
mail-filter/spamass-milter,
mail-filter/spamassassin,
mail-filter/spamassassin-botnet,
mail-filter/spamassassin-fuzzyocr,
mail-filter/spambayes,
mail-filter/spamdyke,
mail-filter/spampd,
mail-filter/spamprobe,
mail-filter/sqlgrey,
mail-filter/tmda
# 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