Splitting up bluez in a sane way, was Re: Task-base is big :(

[Koen Kooi <k.kooi@student.utwente.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Koen Kooi schreef:
> Dr. Michael Lauer schreef:
>> Detlef Vollmann wrote:
>>> The difference to the original python .bb is the removing of
>>>  DEPEND: tk
>>>   This would build a whole X11 system, and I definitely don't want that.
>> Hmm, I'm sure it's just an example for you, but anyway I can't leave
>> it unsaid: Python's dependency on Tk just drags in libx11 and libxext
>> at build time -- I don't see this as being a problem, since they don't
>> end up the image unless you want to.
> 
> And bluez-utils is exactly the same.

What can be done is to make the default bluez-utils build only build bluez-utils* and have
seperate recipes for all the 3rdparty stuff it builds:

FILES_${PN}-alsa = "${libdir}/alsa-lib/libasound*"
FILES_bluez-cups-backend = "${libdir}/cups/backend/bluetooth"

That would solve both buildtime and runtime issues.

What do you think?

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFG6jaFMkyGM64RGpERApT1AKCd2c3/aLUbt2Tq6nf8Dy1GCTl8aACfWqE7
M4/wIIN/uJky4n1rqdGS7C0=
=o+aN
-----END PGP SIGNATURE-----