e63aa5b056
Use ${PN} rather than dhcp to keep align with oe-core to fix:
WARNING: oe-core/meta/recipes-connectivity/dhcp/dhcp_4.3.4.bb: Variable key SYSTEMD_AUTO_ENABLE_${PN}-client (enable) replaces original key SYSTEMD_AUTO_ENABLE_dhcp-client (disable).
WARNING: oe-core/meta/recipes-connectivity/dhcp/dhcp_4.3.4.bb: Variable key SYSTEMD_SERVICE_${PN}-client (dhclient.service) replaces original key SYSTEMD_SERVICE_dhcp-client (dhclient.service).
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
||
|---|---|---|
| .. | ||
| conf | ||
| oe-core | ||
| recipes-core/systemd | ||
| README | ||
This layer depends on:
URI: git://github.com/openembedded/oe-core.git branch: master revision: HEAD
And we're working to break the dependency on this one:
URI: git://github.com/openembedded/meta-oe.git branch: master revision: HEAD
To make BBMASK'ing per layer possible the following directory structure is used:
$[LAYERDIR}//recipes-//.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 -M -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 ' 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 Martin Jansa martin.jansa@gmail.com