On Tue, Mar 12, 2013 at 02:24:30AM -0700, Burton, Ross wrote: > Hi Martin,
Hi Ross, > On 12 March 2013 00:00, Martin Jansa <martin.ja...@gmail.com> wrote: > > And is that correct? I guess some files on target will conflict between > > bluez4 and bluez5, so how is user/distro supposed to upgrade from 4 to > > 5? > > You can't just upgrade from bluez4 to bluez5 like you'd upgrade from > glib 2.10 to glib 2.12 - the API was totally rewritten and the reason > that we're maintaining both is because removing bluez4 would mean > removing bluetooth support is most of the integration points (connman > being the notable exception). > > A distro upgrades from 4 to 5 when they've made the explicit decision > to do so, and changes all of their dependencies to reflect this. That would work with bluez_5.3 with negative D_P too, wouldn't it? Now they need to refine RREPLACES/RCONFLICTS/RPROVIDES combo in distro config too when they do explicit decision to change bluez version. -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
