On Fri, Aug 17, 2012 at 01:48:45PM +0100, Paul Eggleton wrote: > On Friday 17 August 2012 14:39:16 Martin Jansa wrote: > > Should I file a but to fix DEFAULT_PREFERENCE between layers? > > We've discussed this problem before - the trouble is we would have to change > the way the version preference calculation works, and I'm not sure we will be > able to do that without breaking assumptions that people currently rely upon > in the process. By all means file a bug, but I think coming up with a > practical > solution is going to be tricky. > > > Because there is also use case when newer development version is added > > to e.g. meta-oe with negative D_P and only users who decide to test/use > > that version should get it, if they define P_V for this new version. > > This is also undesirable for meta-oe IMHO - as a general principle, meta-oe > shouldn't be trying to both add additional recipes *and* provide newer/older > versions of recipes that are in OE-Core. Please, let's get the new versions > into OE-Core or if they're too risky/broken for some use cases for that, then > they belong in people's distro layers. (Practically I don't think there are > that many instances of new versions of OE-Core recipes that people want to > use > that would be actually rejected by OE-Core).
What if newer version is needed for recipe which exists only in meta-oe? I had this in meta-efl where webkit-efl was sometimes segfaulting when older stable version of libsoup2.4 was used, upstream solved that by recommending development version of libsoup2.4, but as soon as I've added it to meta-efl everybody (including users which don't use webkit-efl from meta-efl - don't need this libsoup2.4) got it as default. Yes I could have added this libsoup2.4 only to meta-shr (where I had P_V for that) and keep webkit-efl broken for everyone else, or try to add developement version of libsoup2.4 to oe-core.. Cheers, -- Martin 'JaMa' Jansa jabber: [email protected]
signature.asc
Description: Digital signature
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
