[oe-commits] Koen Kooi : meta-systemd: add layer

[git at git.openembedded.org]

Module: meta-openembedded.git
Branch: master
Commit: 86321c31730f5d6159b93da8278c9e00a4c92b14
URL:    http://git.openembedded.org/?p=meta-openembedded.git&a=commit;h=86321c31730f5d6159b93da8278c9e00a4c92b14

Author: Koen Kooi <koen at dominion.thruhere.net>
Date:   Thu May 17 09:30:42 2012 +0200

meta-systemd: add layer

This is where the systemd related recipes and appends are going to live

Signed-off-by: Koen Kooi <koen at dominion.thruhere.net>

---

 meta-systemd/README          |   20 ++++++++++++++++++++
 meta-systemd/conf/layer.conf |   28 ++++++++++++++++++++++++++++
 2 files changed, 48 insertions(+), 0 deletions(-)

diff --git a/meta-systemd/README b/meta-systemd/README
new file mode 100644
index 0000000..efed2ee
--- /dev/null
+++ b/meta-systemd/README
@@ -0,0 +1,20 @@
+This layer depends on:
+
+URI: git://git.openembedded.org/openembedded-core
+branch: master
+revision: HEAD
+
+And we're working to break the dependency on this one:
+
+URI: git://git.openembedded.org/meta-openembedded
+branch: master
+revision: HEAD
+
+Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-oe][meta-systemd]' in the subject'
+
+When sending single patches, please use something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-oe][meta-systemd][PATCH'
+
+You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
+
+Main layer maintainer: Koen Kooi <koen at dominion.thruhere.net>
+
diff --git a/meta-systemd/conf/layer.conf b/meta-systemd/conf/layer.conf
new file mode 100644
index 0000000..d07d2ad
--- /dev/null
+++ b/meta-systemd/conf/layer.conf
@@ -0,0 +1,28 @@
+# It really depends on order of the layers appearing in BBLAYERS
+# variable in toplevel bblayers.conf file, where bitbake will search
+# for .inc files and others where bitbake uses BBPATH since it will
+# search the directories from first to last as specified in BBPATH
+# Therefore if you want a given layer to be considered high priority
+# for the .inc and .conf etc. then consider it adding at the beginning
+# of BBPATH. For bblayers bitbake will use BBFILES_PRIORITY to resolve
+# the recipe contention so the order of directories in BBFILES does 
+# not matter.
+
+# We have a conf and classes directory, append to BBPATH
+BBPATH .= ":${LAYERDIR}"
+
+# We have a recipes directory, add to BBFILES
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend"
+
+BBFILE_COLLECTIONS += "systemd-layer"
+BBFILE_PATTERN_systemd := "^${LAYERDIR}/"
+
+# Define the priority for recipes (.bb files) from this layer,
+# choosing carefully how this layer interacts with all of the
+# other layers.
+
+BBFILE_PRIORITY_systemd-layer = "7"
+
+SIGGEN_EXCLUDERECIPES_ABISAFE += " \
+  systemd-serialgetty \
+"