[OE-core] [PATCH 0/2] Remove older GTK+ versions

Paul Eggleton paul.eggleton at linux.intel.com
Fri Aug 17 13:08:27 UTC 2012


On Friday 17 August 2012 14:54:27 Martin Jansa wrote:
> On Fri, Aug 17, 2012 at 01:48:45PM +0100, Paul Eggleton wrote:
> > 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..

That is an unfortunate situation - surely one possible solution though would 
be to backport the actual patch that fixes the problem to the version of the 
library in OE-Core until the development version of the library gets released? 
Alternatively, in certain cases of poorly maintained upstreams where releases 
are infrequent, we have just switched to the development version at a chosen 
revision in OE-Core (after sufficient testing, naturally).
 
I appreciate there are going to be outliers, but I think the majority of 
situations could be handled without making meta-oe introduce unexpected 
changes when it is enabled on top of OE-Core.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre




More information about the Openembedded-core mailing list