Stop using CHROME_BUILD altogether - companion change coming in crostools.

chromeos_version.sh

Index: chromeos_version.sh
diff --git a/chromeos_version.sh b/chromeos_version.sh
index fcebafb516e15b85a6e22b49fc0746ee0dd0a344..649898719e68ce9951777587ef63a5dc9819bd4f 100755
--- a/chromeos_version.sh
+++ b/chromeos_version.sh
@@ -84,9 +84,8 @@ export CHROMEOS_VERSION_STRING=\
 # Set CHROME values (Used for releases) to pass to chromeos-chrome-bin ebuild
 # URL to chrome archive
 export CHROME_BASE=
-# directory containing chrome-chromeos.zip - an svn rev or a full version
-export CHROME_BUILD=
-export CHROME_VERSION="$CHROME_BUILD"
+# export CHROME_VERSION from incoming value or NULL and let ebuild default
+export CHROME_VERSION="$CHROME_VERSION"

[scottz-goog, 2010/11/12 23:51:23]

So other scripts are calling this with
CHROME_VERSION ./chromeos_version.sh? 

It seems more like the caller should be exporting CHROME_VERSION?

[David McMahon, 2010/11/13 00:38:06]

Well this is kind of a hack on a hack.  --chromebuild= was removed from
build_packages in prep for a future mechanism, so in the mean-time we need to
have some way to pass in a chrome version to build_packages (which sources
chromeos_version.sh).  In the case of a branch, CHROME_VERSION in
chromeos_version.sh gets written explicitly with the Chrome version for that
branch.  In the case of ToT, it is set in cbuild and needs to be passed down
through to the ebuild and needs to be exported.  It could be exported by the
caller (cbuild), but I'd rather keep the setting simple at the highest level and
let the build scripts handle any additional requirements (exporting) for now
until whatever future mechanism is put in place.

 
 # Print (and remember) version info.
 echo "ChromeOS version information:"