[OE-core] [PATCH] sanity: Improve configuration upgrade capabilities (support meta-yocto -> poky transition)

[Richard Purdie]

On Sun, 2016-02-28 at 13:20 +0100, Andreas Müller wrote:
> On Sun, Feb 28, 2016 at 11:53 AM, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
> > Right now, only one configuration file can be processed
> > (conf/bblayers.conf)
> > and it can only have one version number. This is a cause of immense
> > friction
> > between OE-Core and Poky since if one needs a version change, it
> > shouldn't
> > be forced on the other.
> > 
> > We'd like to rename the meta-yocto layer (within the meta-yocto
> > repository)
> > to meta-poky. To do this, we need to correct the bblayers.conf file
> > and that
> > means changing the sanity version. After the pain this caused the
> > last time,
> > Paul made me promise never to have them out of sync between OE-Core
> > and Poky,
> > equally, having every distro changing config update OE-Core isn't
> > scalable
> > either.
> > 
> > This patch changes the sanity upgrade method to list a more generic
> > format:
> > 
> > <config file>:<current version variable name>:<required version
> > variable name>:<upgrade function>
> > 
> > This in theory allows us to support upgrades to any of the core
> > configuration files, and allow layers to extend them as needed.
> > Files
> > with the same name can be handled in different layers by setting a
> > unique
> > version name variable in the file itself. The upgrade code is only
> > called
> > if the version variable is set.
> > 
> > To allow us to make the poky name change and use a new
> > configuration file
> > name, one last version bump is included for poky to handle the
> > transition.
> > 
> > Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
> > 
> > diff --git a/meta/classes/sanity.bbclass
> > b/meta/classes/sanity.bbclass
> > index 49693e7..a0553ee 100644
> > --- a/meta/classes/sanity.bbclass
> > +++ b/meta/classes/sanity.bbclass
> 
> I think this breaks parsing. Have reverted it and can build again.

Sorry, I missed a version number change. I've pushed a fix.

Cheers,

Richard