Re: Splitting meta-oe

[Paul Eggleton <paul.eggleton@linux.intel.com>]

On Wednesday 25 January 2012 15:10:18 Martin Jansa wrote:
> I don't see problems as it's now and I fear that splitting it even more
> will result only in more complexity.

We deal with a high-level of complexity in OE, I don't think there's any 
getting away from it; and I'm not entirely convinced this is a significant 
increase. Debugging a build failure can be pretty complex - it can be a 
complete showstopper for someone just getting started, so let's try to avoid 
at least one class of failure that we can fairly easily avoid.

> If there are problems with some recipes then we should try to fix them
> no matter in which even smaller layer they belong.

Sure, this always applies. I just think it would be a worthwhile effort to 
reduce the likelihood of people coming across unexpected failures in parts of 
the system they don't need or would rather not have to debug themselves.
 
> I think we should rather address that issue with layer "priority" which
> should be easier to understand and adjust in bblayers.conf.

This is fine for advanced users like you and me who would know that adding a 
layer has introduced something they don't need and they should just adjust the 
priority to fix it. For the uninitiated, priority values in bblayers.conf will 
be yet more knobs they have to adjust before their build will work.

> And that DEFAULT_PREFERRENCE should be respected across layers, IIRC if
> you add newer less-well tested version of some recipe (like I did with
> libsoup-2.4 in meta-efl) then it's preferred over "stable" version in
> oe-core even when it has lower D_P -1.

I agree that in its most common usage DEFAULT_PREFERENCE is likely to be more 
valuable independent of the layer priority - we should consider this. The 
usefulness in this context is of course dependent on people actually setting 
DEFAULT_PREFERENCE = "-1" when they add the new recipe however.
 
> And we should continue to replace .bb files which exists in meta-oe and
> also in oe-core with .bbappends.

Agreed.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre