<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-openembedded.git/meta-oe/recipes-connectivity/bluez/bluez4-4.101/install-test-script.patch, branch zeus</title>
<subtitle>Mirror of git.openembedded.org/meta-openembedded</subtitle>
<id>https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=zeus</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=zeus'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/'/>
<updated>2017-08-13T11:21:00+00:00</updated>
<entry>
<title>bluez4: remove bluez4-only recipes</title>
<updated>2017-08-13T11:21:00+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2017-07-24T17:25:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=007498ac72e26e9f7064de74f7fe96e91ae6c969'/>
<id>urn:sha1:007498ac72e26e9f7064de74f7fe96e91ae6c969</id>
<content type='text'>
* 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 &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>bluez collection: add (moved from oe-core)</title>
<updated>2015-05-11T08:25:53+00:00</updated>
<author>
<name>Cristian Iorga</name>
<email>cristian.iorga@intel.com</email>
</author>
<published>2015-04-28T09:17:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=3ad735b7e26d5f2acc7452de563db93f8d10340c'/>
<id>urn:sha1:3ad735b7e26d5f2acc7452de563db93f8d10340c</id>
<content type='text'>
BlueZ 4.x Bluetooth stack has been removed from oe-core.
However, it is still supported, so add it to
recipes-connectivity in meta-oe.

meta-systemd layer bluez4 bbappend has been integrated
into bluez4 recipe.

In order to use it in oe-core/poky/YP, 'bluez5' backfill
distro feature needs to be disabled via:
DISTRO_FEATURES_BACKFILL_CONSIDERED = "bluez5" .
'bluetooth' distro feature needs to be present also.

Signed-off-by: Cristian Iorga &lt;cristian.iorga@intel.com&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
</feed>
