[oe-commits] Richard Purdie : os-release: Exclude DATETIME from sstate signature

[git at git.openembedded.org]

Module: openembedded-core.git
Branch: master-next
Commit: 45af748af367e85b4320319b334c72ee961e67e4
URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=45af748af367e85b4320319b334c72ee961e67e4

Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date:   Tue Aug 25 17:58:55 2015 +0100

os-release: Exclude DATETIME from sstate signature

I'm torn over this, I can see someone wanting this to vary in each
build. What pushed me to believe its incorrect in its current form
is that it changes for every MACHINE build, making a complete mess
if you try and generate package feeds using it.

The alternative would be to give up on allarch in this case and make
it MACHINE specific which at least would then be more consistent when
the package makes it to a package feed. If someone wants to do that,
the can propose another patch but this change at least make package
feed usage 'sane' again and avoids the perpetual rebuilds.

Incidentally, its worth noting that changes in source metadata revision
used for the build and included in this recipe would still trigger
rebuilds which is likely the common use case people actually care about.

Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>

---

 meta/recipes-core/os-release/os-release.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/os-release/os-release.bb b/meta/recipes-core/os-release/os-release.bb
index 87fea6f..10a4570 100644
--- a/meta/recipes-core/os-release/os-release.bb
+++ b/meta/recipes-core/os-release/os-release.bb
@@ -21,6 +21,7 @@ VERSION = "${DISTRO_VERSION}${@' (%s)' % DISTRO_CODENAME if 'DISTRO_CODENAME' in
 VERSION_ID = "${DISTRO_VERSION}"
 PRETTY_NAME = "${DISTRO_NAME} ${VERSION}"
 BUILD_ID ?= "${DATETIME}"
+BUILD_ID[vardepsexclude] = "DATETIME"
 
 python do_compile () {
     with open(d.expand('${B}/os-release'), 'w') as f: