Hello all, I will test today an install path for bluez5 using the opkg manager in a existent image.
I will keep you updated. Regards, Cristian -----Original Message----- From: openembedded-core-boun...@lists.openembedded.org [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Burton, Ross Sent: Monday, March 25, 2013 7:15 PM To: Martin Jansa Cc: Koen Kooi; openembedded-core@lists.openembedded.org Subject: Re: [OE-core] [PATCH V3 0/2] BlueZ 5.3 new package On 25 March 2013 17:03, Martin Jansa <martin.ja...@gmail.com> wrote: > But opkg will still error out because of missing RPROVIDES, no? I'll admit that I didn't test an upgrade path, but the scenario I can see actually happening is that the distro flips its applications from bluez4 to bluez5 so they rdepend on bluez5 now. bluez5 will get pulled in through that dependency, nothing depends on bluez4 anymore, so opkg should remove bluez4. bluez4 and bluez5 don't expose the same ABI so they are not suitable RPROVIDES for eachother. Ross _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
