From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] sanity: Improve configuration upgrade capabilities (support meta-yocto -> poky transition)
Date: Sun, 28 Feb 2016 15:59:42 +0000 [thread overview]
Message-ID: <1456675182.11498.163.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALbNGRTTAz=UfaXLEOjzdc5K_v7R3=OL8abzQQXq=97YkcofUA@mail.gmail.com>
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@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@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
next prev parent reply other threads:[~2016-02-28 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 10:53 [PATCH] sanity: Improve configuration upgrade capabilities (support meta-yocto -> poky transition) Richard Purdie
2016-02-28 12:20 ` Andreas Müller
2016-02-28 15:59 ` Richard Purdie [this message]
2016-02-28 21:11 ` Martin Jansa
2016-02-28 22:54 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1456675182.11498.163.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox