From b9fbc85938deaa18354cefa548026d3dc966e5c2 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Thu, 21 Apr 2011 11:39:34 +0100 Subject: [PATCH] bitbake.conf: Only very weakly assign SRCREV to the default of INVALID This means it can easily be overridden by other points in the code, such as a ?= assignment in recipes. (From OE-Core rev: f370961b61be2e2be4e7b33c446d71c0693ca16b) Signed-off-by: Richard Purdie --- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index 2e4a76d2c2..c2a072a329 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf @@ -522,7 +522,7 @@ UPDATECOMMAND = "ERROR, this must be a BitBake bug" UPDATECOMMAND_cvs = "/usr/bin/env cvs -d${CVSROOT} update -d -P ${CVSCOOPTS}" UPDATECOMMAND_svn = "/usr/bin/env svn update ${SVNCOOPTS}" SRCDATE = "${DATE}" -SRCREV = "INVALID" +SRCREV ??= "INVALID" AUTOREV = "${@bb.fetch2.get_autorev(d)}" SRCPV = "${@bb.fetch2.get_srcrev(d)}"