[Openembedded-architecture] Yocto Compatible 2.0 + signature changes

[Trevor Woerner]

If simply adding a Yocto Compatible 2.0 layer to a build doesn't cause
any of its *bbappends to affect the build by default, but simply
adding any other (presumably non Yocto Compatible 2.0) layer to a
build has the potential to affect the build simply by virtue of having
added the layer, wouldn't that be horribly confusing for users?

Shouldn't this sort of complete reversal of policy regarding layers be
something that's enforced by the tool (bitbake) so that either all
layers affect the build simply by virtual of being added, or they
don't?