" why having it be so is not a very good thing." Sorry, I did not understood this part.
Judging by my investigation, is RREPLACES needed or not? /Cristian -----Original Message----- From: Phil Blundell [mailto:p...@pbcl.net] Sent: Tuesday, July 16, 2013 5:34 PM To: Iorga, Cristian Cc: openembedded-core@lists.openembedded.org Subject: Re: [OE-core] [PATCH V3 0/2] BlueZ 5 experimental recipes On Tue, 2013-07-16 at 17:28 +0300, Cristian Iorga wrote: > Observe my investigation below in order to decide if RREPLACES is needed. > Conclusion: BlueZ 5.x will be eventually an upgrade path for an > already installed embedded device. As such, RREPLACES is needed for a > system-wide upgrade. It wasn't very obvious to me that these results make a compelling case for bluez4 needing to RREPLACE bluez5. Indeed, this section: root@qemux86:~# opkg install bluez5 Multiple replacers for bluez5, using first one (bluez4). Package bluez4 is already installed on root. root@qemux86:~# opkg list-installed | grep bluez bluez4 - 4.101-r6.0 libasound-module-bluez - 4.101-r6.0 ... seems to illustrate (modulo the usual amount of opkg craziness) why having it be so is not a very good thing. p. _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
