From 6224cba9c76c34cad99cc310d06d069d77261719 Mon Sep 17 00:00:00 2001 From: Chris Masone Date: Wed, 18 May 2011 14:30:47 -0700 Subject: [PATCH] [crosutils] Make chromium/libcros mismatch messages more semantically accurate The messages printed out by the code that checks if chromium's libcros and the system's libcros are in sync were kind of confusing and not quite accurate. The system library implements a range of API versions, and it is chromium that requires a particular version of the API. The messages now clearly reflect this. BUG=None TEST=manual Change-Id: I7308d7eb724edfb7fa11edbe0fbec86ee12c5afe Reviewed-on: http://gerrit.chromium.org/gerrit/1136 Reviewed-by: David James Tested-by: Chris Masone --- test_build_root | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/test_build_root b/test_build_root index d642b3282b..2965b4cba7 100755 --- a/test_build_root +++ b/test_build_root @@ -100,14 +100,14 @@ check_cros_version() { if [ "$MIN_VERSION" -gt "$VERSION" ]; then echo "test_build_root: System libcros not compatible with Chromium." - echo "Chromium has version $VERSION, but system requires $MIN_VERSION or" - echo "later." + echo "Chromium requires version $VERSION, but system provides $MIN_VERSION" + echo "or later." return 1 fi if [ "$VERSION" -gt "$MAX_VERSION" ]; then echo "test_build_root: System libcros not compatible with Chromium headers." - echo "Chromium has version $VERSION, but system requires $MAX_VERSION or" - echo "earlier." + echo "Chromium requires version $VERSION, but system provides $MAX_VERSION" + echo "or earlier." return 1 fi return 0