meta-openembedded/meta-systemd
Khem Raj ba9aae5594 gitpkgv.bbclass: Add a symlink from meta-oe
This is for systemd layer to be used with
out depending on meta-oe eventually gitpkgv
or similar solution should come out of OE-Core

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
2012-08-07 12:21:24 +02:00
..
classes gitpkgv.bbclass: Add a symlink from meta-oe 2012-08-07 12:21:24 +02:00
conf layer.conf/README: search directory structure for bbappends changed 2012-07-16 09:39:05 +02:00
meta-efl/recipes-efl/efl elsa: move systemd support to meta-systemd 2012-07-16 09:39:06 +02:00
meta-gnome/recipes-gnome/gdm gdm: move systemd support to meta-systemd 2012-07-16 09:39:05 +02:00
meta-oe gpsd: drop older version 3.4 2012-07-28 22:45:47 +02:00
oe-core/recipes-multimedia/pulseaudio meta-systemd: pulseaudio: rename bbappend to match new oe-core version 2012-07-19 19:54:30 +02:00
recipes-core/systemd systemd-compat-units: move list of disabled services to variable, fix hwclock.sh and output 2012-08-07 12:21:23 +02:00
recipes-extended/pam libpam 1.1.5 bbappend: register PAM session with logind 2012-07-17 08:52:13 +02:00
README layer.conf/README: search directory structure for bbappends changed 2012-07-16 09:39:05 +02:00

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

To make BBMASK'ing per layer possible the following directory structure is
used:

$[LAYERDIR}/<layer name>/recipes-<group-name>/<recipe-name>/<recipe-name>.bbappend

Send pull requests to openembedded-devel@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@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@dominion.thruhere.net>