[oe] Splitting meta-oe

[Khem Raj]

On Thu, Jan 26, 2012 at 1:02 AM, Martin Jansa <martin.jansa at gmail.com> wrote:
>
> 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.

yes thats a good thing to do. But I still would prefer a layer separation
from meta-oe
>
> 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).
>

yes meta-deprecated by default should be added to BBMASK

> Cheers,
>
> --
> Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com