[oe] OE recipe tree quality

[Frans Meulenbroeks]

2010/8/1 Richard Purdie <rpurdie at rpsys.net>

>
>
> "world" is used by Poky quite successfully. In Poky we expect everything
> to build with a known list of things that don't. Our aim is to have that
> list consisting of zero items and I intend to see that happens :).
>

I would love the see this happen for OE as well.

>
> I don't think many people have been watching Poky recently but we've
> been quietly having a massive quality control effort on the metadata in
> there. This has included:
>
> a) Removal of legacy staging
> b) Using BBCLASSEXTEND = native where it makes sense
> c) Using nativesdk (no sdk class)
> d) Upgrading everything to modern versions of the package concerned
> e) Only allowing sane pkgconfig files
> f) Enhancing the metadata with licence and other information
>

Cool. I'll peek into it.

>
> Its possible to contemplate this due to Poky's version policy and size
> and its still taking significant effort. OE has always been pulled in
> many directions and this is both a good and a bad thing. The only ways I
> can think of to make a dramatic improvement to OE in this area would be
> disliked by some of its users so I don't know what the solution is.
>

*Any* solution (including the current status) will be disliked by some
users.
We need to set a direction. I hope and suggest the TSC will provide some
guidance here.

We can e.g. keep complaining about legacy staging, but if there is no action
nothing will change.

I'm trying to create awareness and do suggestions on how to resolve things.
Unfortunately these are rejected by some, but at the same time these very
same persons fail to provide an alternative scenario (apart from that
*others* need to work on this.

>
> There are other good things happening in Poky as well as the above too
> btw :)
>

I'll keep an eye on it!

Frans