On 11.02.21 15:59, Richard Purdie wrote:

On Thu, 2021-02-11 at 15:47 +0100, Konrad Weihmann wrote:

quoted

On 11.02.21 14:04, Richard Purdie wrote:

quoted

On Thu, 2021-02-11 at 13:10 +0100, Konrad Weihmann wrote:

quoted

On 11.02.21 12:43, Richard Purdie wrote:

quoted

On Thu, 2021-02-11 at 08:21 +0100, Konrad Weihmann wrote:

quoted

After this patch got merged I notice some "noise" in my builds.

I can guarantee that making any such option available will just have
people reach for it and use it. You clearly want to here when the
changes needed to avoid it are probably not that difficult.

quoted

If that's not what the project wants, I'm also fine with it, but then it
would be really helpful to point to the bbappend as a culprit and not
the base recipe

I understand why you'd want it, I'm just not sure if would encourage
the right behaviour :(.

Fair enough - guess I will go with the educating ppl (including myself)
path then

One thing to remember is that you can change ERROR_QA and WARN_QA on a
per recipe basis, so in theory you can disable this per recipe, or
reduce it to a warning...

Its not neat code to do it, but it isn't really meant to be!

Yeah, unfortunately all the CI tooling I use, will even reflect that 
back to the user - nvm I will figure out something

Cheers,

Richard