This goes back to my RFC: http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/39016
As we are removing meta-toolchain* and replacing it with bitbake <imagename> -c populate_sdk this causes issues with those of us who need to do automated builds both on the current development branch and on prior development branches. Example: For prior releases, I need to build meta-toolchain*. Without having a simple way to figure out where this is no longer the case, I (and other folks who run automated builds) end up having to jump through a lot of hoops trying to figure out where this layer changed. Utilizing LAYERVERSION_* to do it makes sense as there is a significant change that would cause issues for build engineers. Prior to this I was utilizing LCONF, which was the wrong solution, but just happened to work in the example I'm thinking of. -b On Tue, Jul 2, 2013 at 11:54 AM, Phil Blundell <p...@pbcl.net> wrote: > On Tue, 2013-07-02 at 10:45 -0700, Elizabeth Flanagan wrote: >> Bumping LAYERVERSION_core to denote where meta-toolchain* is being >> depreciated. > > This commit message doesn't provide much explanation of what exactly is > going on and why this constitutes "significant changes that will > cause compatibility issues with other layers". Can you clarify? > > thanks > > p. > > -- Elizabeth Flanagan Yocto Project Build and Release _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
