From 41053141cdc04fd6d8490b54b8b8dc59dc0fe93a Mon Sep 17 00:00:00 2001 From: Elizabeth Flanagan Date: Tue, 2 Jul 2013 15:29:29 -0700 Subject: layer.conf: Bumping LAYERVERSION_core Bumping LAYERVERSION_core to denote where meta-toolchain* is being depreciated. 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 -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 Signed-off-by: Saul Wold --- meta/conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'meta/conf/layer.conf') diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf index a112e8632a..a834765563 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}/../")}' -- cgit v1.2.3