On 13 March 2013 02:14, Koen Kooi <k...@dominion.thruhere.net> wrote: > At the risk of sounding snarky while making a real recommendation: Why not do > it oe-core > style and completely remove bluez 4.x at the start of the 1.5 > cycle and work through the > breakage? I guess that means I volunteer to help with that :)
Is the world going to migrate to the bluez5 API in six months? I was expecting to have to carry bluez4 and 5 for at least one or two cycles. We have a similar issue with GStreamer 0.10 and 1.0 - we could drop 0.10 and port what ships in oe-core, but the subsequent breakage would cause a riot. Ross _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
