[oe] Splitting meta-oe

[Martin Jansa]

On Thu, Jan 26, 2012 at 03:45:52PM +0100, Frans Meulenbroeks wrote:
> 2012/1/26 Martin Jansa <martin.jansa at gmail.com>
> 
> > On Wed, Jan 25, 2012 at 06:33:13PM +0100, Frans Meulenbroeks wrote:
> > > I like the idea of putting toolchains in a layer.
> > >
> > > Wrt DP = -1:
> > > I feel if a recipe needs DP = -1 it is not good enough to be added to
> > > meta-oe. Probably it is more something for an unstable layer.
> > > (and DP = -1 encourages the growth of deadwood; I still recall in OE that
> > > there were some recipes that had the last 3 or 4 versions all with DP =
> > -1;
> > > let's try to avoid this in oe-core/meta-oe)
> >
> > I'm not proposing to stash multiple versions of same recipe with D_P in
> > same layer.
> >
> > What I'm missing is use-case when for example with libsoup-2.4 I'm
> > adding unstable version, because actually webkit-efl has random runtime
> > crashes with stable version, but works better with unstable one.
> >
> > So I want to be able to add recipe with D_P = -1 which would say, that
> > this recipe is not used unless someone really wants and adds P_V to his
> > layer to get it (I guess people using browsers based on webkit-efl).
> >
> > But right now it will pick this unstable version from meta-oe by default
> > and you have to add P_V for that stable version in oe-core (and keep it
> > up2date as long as stable version in oe-core is updated).
> >
> > And I guess the same use-case D_P should be used for all "not so well
> > tested" or "deprecated" recipes in meta-oe or any other layer.
> >
> > Even if there is meta-deprecated layer.. I guess nobody would prefer all
> > deprecated recipes, but just some of them (ideally by pinning them with
> > P_V).
> >
> >
> > HI Martin,
> 
> I understand your reasoning.
> My main concerns are:
> - you might end up with lots of versions and no one knows that is actually
> used (so it is difficult to clean it). We saw this in oe classic

I don't see this happening in oe-core or meta-oe, your grep proves it.

> - generally the reasons why a recipe has DP -1 are unclear. How would Joe
> Average know that if he is using webkit-efl he is better off using this new
> libsoup recipe?

Reading it about DP setting or in commit where I've added it?

> - and if a recipe is not well enough tested it should probably not end up
> in meta-oe anyway (but better e.g. in meta-oe-next or meta-oe-new or
> whatever you want to call the super bleeding edge version)

How will Joe Average know that because of webkit-efl he should enable
meta-efl-next (or
oe-core-next-libsoup-development-version-alpha-centauri-edition layer) 
 if he doesn't even know what's happening in layers he is
using already (meta-efl for webkit-efl)?

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20120126/a671418c/attachment-0002.sig>