commit b926fc2c2424735b84d1250394234b3b4bcf577c
author Vic (Chun-Ju) Yang <victoryang@chromium.org> Fri Jan 24 15:28:06 2014 +0800
committer chrome-internal-fetch <chrome-internal-fetch@google.com> Sat Jan 25 09:06:22 2014 +0000
tree 90ebb4094a89e80b5f65894d7236c8e19cc6dc9f
parent 981164c327a5f249b73adb853d2209cc9da91e56

Include board name and version in factory toolkit ID string

This makes it easier to tell which factory toolkit it is.

BUG=chrome-os-partner:24798
TEST=Manual w/ and w/o version string

Change-Id: I138ffff1c6d6d893138de6b5baefa3550288e92f
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/183764
Reviewed-by: Jon Salz <jsalz@chromium.org>

make_factory_toolkit.sh

diff --git a/make_factory_toolkit.sh b/make_factory_toolkit.sh
index 26a433e..1d3a792 100755
--- a/make_factory_toolkit.sh
+++ b/make_factory_toolkit.sh
@@ -17,6 +17,8 @@
 DEFINE_string board "${DEFAULT_BOARD}" \
   "The board to build a factory toolkit for."
 DEFINE_string output_dir "" "Path to the folder to store the factory toolkit."
+DEFINE_string version "" \
+  "The version tag to be included in the identification string."
 
 cleanup() {
   sudo rm -rf "${temp_pack_root}"
@@ -48,10 +50,14 @@
   emerge-${FLAGS_board} --root="${temp_pack_root}" --nodeps --usepkgonly -v \
     chromeos-factory chromeos-factory-board autotest-factory-install
 
+  if [[ -n "${FLAGS_version}" ]]; then
+    local id_str="${FLAGS_board} Factory Toolkit ${FLAGS_version}"
+  else
+    local id_str="${FLAGS_board} Factory Toolkit"
+  fi
+
   local output_toolkit="${output_dir}/install_factory_toolkit.run"
-  makeself --bzip2 --nox11 "${temp_pack_root}" \
-    "${output_toolkit}" \
-    "Factory Toolkit" \
+  makeself --bzip2 --nox11 "${temp_pack_root}" "${output_toolkit}" "${id_str}" \
     usr/local/factory/py/toolkit/installer.py
 
   echo "