On 25 March 2013 16:09, Koen Kooi <[email protected]> wrote: > So you say it's not an upgrade path, but... > >> - bluez5 conflicts with/replaces bluez4. > > ... here you add RREPLACES. Why is that?
The logic was that if a *distro* does the upgrade from bluez4 to bluez5, the package manager needs to be able to remove bluez4 when installing bluez5, as otherwise they'd just conflict and the package manager would error out. Ross _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
