[Openembedded-architecture] Yocto Compatible 2.0 + signature changes

[Patrick Ohly]

On Thu, 2017-05-11 at 09:50 -0400, Trevor Woerner wrote:
> I've re-read these emails carefully and I see where my confusion came in.
> 
> First off I had never heard of conditional bbappends and am surprised
> to learn of them.

As you correctly point out, the existing documentation doesn't describe
any of the techniques that are needed to make bbappends conditional, and
it also doesn't warn about the negative effect on re-usability when
using .bbappends liberally.

Once the overall project agrees that this is creating a problem that
needs to be addressed and the necessary tooling exists to help layer
maintainers, then the documentation will have to be updated to reflect
this.

> It's true, however, that I'm not as familiar with the guts of bitbake
> etc as other are. And it is true that I tend to use OE to take
> openembedded-core + a BSP layer and go from there. I don't tend to get
> into all the fancy stuff other people do and I don't have the depth of
> experience others have. So it's not entirely crazy to think that I've
> never heard of conditional bbappends and I do think it might be
> confusing to some people when some bbappends apply automatically and
> others don't, and the only way to tell the difference is to examine
> each line of a bbappend to determine how it will behave.

Each layer should have instructions on how to use it. Developers adding
a layer should read that. That's not new, already now there are layers
were additional steps besides just adding the layer are needed (example:
meta-clang).

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.