[app-pda] new particle

weekly/app-pda.particle

@@ -0,0 +1,111 @@
+# 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-pda/barry,
+	app-pda/coldsync,
+	app-pda/dynamite,
+	app-pda/fusepod,
+	app-pda/gnupod,
+	app-pda/gpixpod,
+	app-pda/gtkpod,
+	app-pda/ideviceinstaller,
+	app-pda/ifuse,
+	app-pda/iripdb,
+	app-pda/jpilot,
+	app-pda/jpilot-backup,
+	app-pda/jpilot-mail,
+	app-pda/jpilot-plucker,
+	app-pda/jpilot-syncmal,
+	app-pda/libimobiledevice,
+	app-pda/libopensync,
+	app-pda/libopensync-plugin-file,
+	app-pda/libopensync-plugin-google-calendar,
+	app-pda/libopensync-plugin-irmc,
+	app-pda/libopensync-plugin-moto,
+	app-pda/libopensync-plugin-palm,
+	app-pda/libopensync-plugin-python,
+	app-pda/libopensync-plugin-sunbird,
+	app-pda/libplist,
+	app-pda/libsyncml,
+	app-pda/msynctool,
+	app-pda/orange,
+	app-pda/p3nfs,
+	app-pda/pilot-link,
+	app-pda/synce-connector,
+	app-pda/synce-sync-engine,
+	app-pda/syncevolution,
+	app-pda/usbmuxd
+
+# 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