Re: 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:
> Marcin Juszkiewicz schreef:
>> Dnia sobota, 15 września 2007, Koen Kooi napisał:
>>> Koen Kooi schreef:
>>>> Marcin Juszkiewicz schreef:
>>>>> Dnia piątek, 14 września 2007, Koen Kooi napisał:
>>>>>> 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:
>>>>>> That would solve both buildtime and runtime issues.
>>>>>>
>>>>>> What do you think?
>>>>> bluez-utils-cups, bluez-utils-gstreamer, bluez-utils-alsa? Sounds
>>>>> good for me - especially first both.
>>>> bluez-utils-cups and bluez-utils-alsa can be done for sure, but I
>>>> haven't looked at where gstreamer comes in and if it can be a
>>>> seperate package.
>>> What do you think of this patch?
>> Looks ok - in cups you can disable hid2hci and in both probably few other 
>> options can be disabled but their compile time is small rather so better 
>> leave as they are.
>>
>> Did you tried to create separate gst-plugin-bluez recipe?
> 
> Not yet, I wanted the easy stuff (bluez, alsa) to get seperated first.

Committed, please report (or better fix :) ) any problems with it.

regards,

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

iD8DBQFG8BDaMkyGM64RGpERAgFCAJsGSwSH59nQFio5HIgEfCz9yGzvLACgh65H
cuZPF+12wtemuBh+4J4pxZg=
=j9DI
-----END PGP SIGNATURE-----