From 35431dc239c6e0ce0db6a14e7004d1efccc74d83 Mon Sep 17 00:00:00 2001
From: Colin Watson <cjwatson@canonical.com>
Date: Mon, 25 Jan 2010 16:51:59 +0000
Subject: [PATCH] Handle some special-case naming for chromiumos-build

chromiumos-build gets less confused if we refer to the package name
e4fsprogs-git rather than the directory name e2fsprogs (which is also a
different source package downloadable from Ubuntu).

Don't bother trying to build ibus-anthy, ibus-chewing, or ibus-hangul on
anything other than i386 for now.  They aren't easily cross-buildable
and we can live without input methods.

Review URL: http://codereview.chromium.org/554063
---
 build_platform_packages.sh | 19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

diff --git a/build_platform_packages.sh b/build_platform_packages.sh
index 53923c4a48..0f0a62b207 100755
--- a/build_platform_packages.sh
+++ b/build_platform_packages.sh
@@ -60,7 +60,24 @@ if [ $FLAGS_new_build -eq $FLAGS_TRUE ]; then
   # chromiumos-build works out the build order for itself.
   PACKAGES='dh-chromeos libchrome libchromeos'
   for PKG in $PLATFORM_DIRS $THIRD_PARTY_PACKAGES; do
-    PACKAGES="$PACKAGES ${PKG%/*}"
+    # Handle some special-case naming.
+    case $PKG in
+      e2fsprogs/files)
+        PACKAGES="$PACKAGES e4fsprogs-git"
+        ;;
+      ibus-anthy|ibus-chewing|ibus-hangul)
+        # These are difficult to cross-build right now, and we can live
+        # without them temporarily.
+        if [ "$FLAGS_architecture" = i386 ]; then
+          PACKAGES="$PACKAGES ${PKG%/*}"
+        else
+          echo "WARNING: Skipping $PKG on $FLAGS_architecture"
+        fi
+        ;;
+      *)
+        PACKAGES="$PACKAGES ${PKG%/*}"
+        ;;
+    esac
   done
   verbose chromiumos-build -a "$FLAGS_architecture" --apt-source $PACKAGES
 else