Files
meta-openembedded/meta-oe
Martin Jansa 007498ac72 bluez4: remove bluez4-only recipes
* remove recipes which support only bluez4 and are blacklisted when
  bluez5 is selected in DISTRO_FEATURES, if someone is still using
  bluez4, then it can be restored in separate meta-bluez4 and
  maintained by people using it.

* there are few recipes which support both bluez5 or bluez4 based on
  selected DISTRO_FEATURES, these can stay in meta-oe repository, but
  now people without bluez5 in DISTRO_FEATURES will need to add
  meta-bluez4 layer to satisfy bluez4 dependency

  meta-gnome/recipes-connectivity/obex/obexd_0.48.bb:DEPENDS += "${@bb.utils.contains('DISTRO_FEATURES','bluez5','bluez5','bluez4',d)}"
  meta-gnome/recipes-gnome/gnome-bluetooth/gnome-bluetooth_3.18.2.bb:    ${@bb.utils.contains('DISTRO_FEATURES','bluez5','bluez5','bluez4',d)} \
  meta-oe/recipes-connectivity/obex/obex-data-server_0.4.6.bb:DEPENDS += "${@bb.utils.contains('DISTRO_FEATURES','bluez5','bluez5','bluez4',d)}"
  meta-oe/recipes-connectivity/obex/openobex_1.7.2.bb:DEPENDS_append_class-target = " ${@bb.utils.contains('DISTRO_FEATURES','bluez5','bluez5','bluez4',d)}"
  meta-oe/recipes-connectivity/packagegroups/packagegroup-tools-bluetooth.bb:RDEPENDS_bluez4 = " \
  meta-oe/recipes-connectivity/packagegroups/packagegroup-tools-bluetooth.bb:# Install bluez4 tools or bluez5 tools depending on what is specified in the distro.

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-08-13 13:21:00 +02:00
..
2017-08-13 13:16:18 +02:00
2017-07-24 18:58:54 +02:00
2017-08-13 13:20:57 +02:00
2017-08-13 13:19:41 +02:00

This layer depends on:

URI: git://github.com/openembedded/oe-core.git
branch: master
revision: HEAD

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' 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][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>
                       Martin Jansa <martin.jansa@gmail.com>