meta-openembedded/meta-systemd
Holger Hans Peter Freyther 8ae005d033 systemd: Make the main systemd files proper CONFFILES
Allow a user to edit the main systemd configuration files and have
them not overwritten at the next upgrade of it.

Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
2012-11-13 15:02:57 +01:00
..
classes Replace bb.data.* with d.* 2012-10-28 14:32:06 +00:00
conf layer.conf/README: search directory structure for bbappends changed 2012-07-16 09:39:05 +02:00
meta-efl/recipes-efl/efl meta-systemd: elsa: rename to entrance 2012-08-20 09:57:43 +02:00
meta-gnome/recipes-gnome/gdm gdm: do not hardcode /usr/sbin 2012-09-17 10:42:30 +02:00
meta-multimedia/recipes-multimedia/musicpd mpd: Initial add 0.17.1 2012-09-18 15:54:03 +02:00
meta-oe lighttpd: move systemd appends since recipe is in oe-core 2012-11-13 12:58:07 +01:00
oe-core lighttpd: move systemd appends since recipe is in oe-core 2012-11-13 12:58:07 +01:00
recipes-core/systemd systemd: Make the main systemd files proper CONFFILES 2012-11-13 15:02:57 +01: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>