meta-openembedded/meta-systemd
Andreas Müller 4ac49b2ac2 gdm: do not rely on dev-tty7.device
Error message was:

[ TIME ] Timed out waiting for device dev-tty7.device.
[DEPEND] Dependency failed for Gnome Display Manager.

run tested on overo/xfce

Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
2012-09-17 10:42:29 +02:00
..
classes systemd.bbclass: add option to disable automatic RRECOMMENDS pkg-systemd_base -> pkg-systemd 2012-08-20 10:02:09 +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 meta-systemd: elsa: rename to entrance 2012-08-20 09:57:43 +02:00
meta-gnome/recipes-gnome/gdm gdm: do not rely on dev-tty7.device 2012-09-17 10:42:29 +02:00
meta-oe dnsmasq: add systemd service scripts for dnsmasq 2012-09-10 10:56:49 +02:00
oe-core/recipes-connectivity avahi: use systemd.bbclass for avahi-systemd 2012-09-04 14:49:01 +02:00
recipes-core/systemd systemd: Upgrade to 189 2012-09-08 11:36:53 +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>