[oe] [Angstrom-devel] Opie image compiles

[Paul Eggleton]

Zimler Attila Tamás wrote:
> I masked out all bluez4 recipe and it turned out that
> DISTRO_BLUETOOTH_MANAGER is the source for the problem. When I changed
> it from bluez4 to bluez-utils, opie-image compiles correctly. But this
> change is in opposite direction as Koen changed it on 2009. march 31.
> How should we solve this correctly?
>
> I see two possible solution:
> 1) The best would be to migrate opie-image to bluez4, for this I don't
> know if softwares in opie-image are ready for bluez4.
> 2) If the above is impossible then conditionally replace the
> DISTRO_BLUETOOTH_MANAGER in opie-image to bluez-utils. But in this case
> the possibility of forgetting old bluez-utils in opie-image after
> softwares are ready for bluez4 still exists.

I am not yet clear on whether there are issues with using bluez4 together
with Opie, I have not yet tested it (I imagine there probably are problems
- help here would be very welcome). However I will state categorically
that from what I have found checking through the recipes, nothing in Opie
specifically requests bluez3 - it only depends on bluez-libs and
bluez-utils. If bluez4 does not provide both of these then it needs to be
fixed, or at least we should work out the changes to the Opie recipes that
are needed such that it correctly follows the version selected in the
configuration.

Allow me to rant for a second: this is not the first time that a change
has been introduced into OE that causes severe breakage for other users,
where the person(s) responsible for the change have shown little interest
in sorting out the problems that they have caused. I would hope that
everyone agrees that we should try to minimise (or at the very least
explain clearly) the impact of such changes in the future.

Kind regards,
Paul