[v2] layer.conf: Bumping LAYERVERSION_core

Submitted by Elizabeth Flanagan on July 2, 2013, 10:29 p.m. | Patch ID: 52845


Message ID 1372804169-29269-1-git-send-email-elizabeth.flanagan@intel.com
State New
Headers show

Commit Message

Elizabeth Flanagan July 2, 2013, 10:29 p.m.
Bumping LAYERVERSION_core to denote where meta-toolchain* is being

This goes back to my RFC:


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.

Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
 meta/conf/layer.conf |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Patch hide | download patch | download mbox

diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index a112e86..a834765 100644
--- a/meta/conf/layer.conf
+++ b/meta/conf/layer.conf
@@ -9,7 +9,7 @@  BBFILE_PRIORITY_core = "5"
 # This should only be incremented on significant changes that will
 # cause compatibility issues with other layers
-LAYERVERSION_core = "1"
+LAYERVERSION_core = "2"
 # Set a variable to get to the top of the metadata location
 COREBASE = '${@os.path.normpath("${LAYERDIR}/../")}'