[yocto] [OE-core] [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation

[Richard Purdie]

On Wed, 2017-03-01 at 08:10 +0100, Patrick Ohly wrote:
> On Wed, 2017-03-01 at 04:00 +0000, Richard Purdie wrote:
> > 
> > On Tue, 2017-02-28 at 21:09 +0100, Patrick Ohly wrote:
> > > 
> > > On Mon, 2017-02-20 at 15:12 -0600, Aníbal Limón wrote:
> > > > 
> > > > 
> > > > common.test_signatures: Test executed in BSP and DISTRO layers
> > > > to
> > > > review
> > > >     doesn't comes with recipes that changes the signatures.
> > > I have a question about the goal for this test: is it meant to
> > > detect
> > > layers which incorrectly change the signatures of allarch recipes
> > > or
> > > recipes which share the same tune flags with other machines?
> > > 
> > > Let's take MACHINE=edison as an example.
> > The test is not for these things. Its using the sstate signatures
> > for
> > something different compared to those other tests.
> > 
> > The idea is that if you have a set of layers and generate the
> > signatures for world, then you add say a BSP layer but do not
> > select
> > that MACHINE, the signatures should remain unchanged.
> That's useful too, of course.
> 
> Is the "build single distro for different machines" scenario that I
> described part of the Yocto Compliance 2.0? Should there be tests for
> it?

Right now its not but I'd consider it. The question is can we write an
easy generic test for it, and also clearly phrase the criteria in the
list of compliance questions with a binary yes/no answer?

Cheers,

Richard