[oe] [RFC] Make some big changes right after next stable

Richard Purdie rpurdie at rpsys.net
Thu Mar 4 10:18:39 UTC 2010

On Wed, 2010-03-03 at 09:30 -0700, Tom Rini wrote:
> As many people know, there's a lot of "odd" internal things that OE
> does, that if we had it to do over, we would do differently.  What I
> would like to propose is that in time for the next stable branch we:
> 1: Define a set of DISTROs/MACHINEs/build targets that need to stay
> working

It was commented at OEDEM that it would be nice to have this magic list.
We still don't have one though.

> 2: In a separate branch (per big change), get one of these big, going to
> leave some stuff broken changes
> 3: Define / document what needs to be done before these branches can be
> merged back (something like #1 is working still, and if applicable a
> guide to the common problems/how to fix people are going to run into).

It makes sense.

> What I'm getting at is that this would let us do things like rework the
> "this is where we place things that we build other recipes with" concept
> so that sysroot just works (and otherwise makes more sense again).  Or
> "let us have more consistency in build with compared to what could end
> up on device".  And so on.
> What do people think?  And what would people work on?

This is the problem, it would be you taking this on, you'd be the person
who needed to fix things, then you would get to merge back. I don't
think we have enough people around that people would volunteer to fix
branches like that.

But by all means prove me wrong.



More information about the Openembedded-devel mailing list