Call install-build-deps.sh from install-build-deps-android.sh

build/install-build-deps-android.sh

 #!/bin/bash -e
 
 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # Script to install everything needed to build chromium on android that
 # requires sudo privileges.
 # See http://code.google.com/p/chromium/wiki/AndroidBuildInstructions
 
 # This script installs the sun-java6 packages (bin, jre and jdk). Sun requires
 # a license agreement, so upon installation it will prompt the user. To get
 # past the curses-based dialog press TAB <ret> TAB <ret> to agree.
 
 if ! uname -m | egrep -q "i686|x86_64"; then
   echo "Only x86 architectures are currently supported" >&2
   exit
 fi
 
-if [ "x$(id -u)" != x0 ]; then
-  echo "Running as non-root user."
-  echo "You might have to enter your password one or more times for 'sudo'."
-  echo
-fi
+# Install first the default Linux build deps.
+"$(dirname "${BASH_SOURCE[0]}")/install-build-deps.sh" \

[Nico, 2014/04/03 20:19:56]

Is `$(dirname "${0}") enough? It's not like there's several levels of sourcing
here.

[Primiano Tucci (use gerrit), 2014/04/03 20:54:10]

I think the difference between $0 vs $BASH_SOURCE is that $BASH_SOURCE is safer,
in the sense that it should behave like __file__in python.
Essentially, I fear that if you run the script trhough ". install-build-deps.sh"
oppposite to "./install... or ./build/install...." that might fail.

[Nico, 2014/04/03 20:58:36]

We use $0 in a bunch of places, and I never heard of problems like this.

[Primiano Tucci (use gerrit), 2014/04/03 21:30:31]

~ $ cat foo
#!/bin/bash
echo My dir-1 is $(dirname "${BASH_SOURCE[0]}")/
echo My dir-2 is $(dirname "$0")/

/tmp $ ./foo
My dir-1 is ./
My dir-2 is ./

/tmp $ . foo
My dir-1 is ./
My dir-2 is /bin/ #Ha wrong

/tmp $ /tmp/foo
My dir-1 is /tmp/
My dir-2 is /tmp/

/tmp $ . /tmp/foo
My dir-1 is /tmp/
My dir-2 is /bin/  # Ha wrong again!!!
/tmp $ 

That's it! I think just nobody complained, but BASH_SOURCE is IMHO actually more
reliable.
The real question is why we keep writing bash scripts, but that's another story
:)

+    --no-syms --no-arm --no-chromeos-fonts --no-nacl --no-prompt
 
 # The temporary directory used to store output of update-java-alternatives
 TEMPDIR=$(mktemp -d)
 cleanup() {
   local status=${?}
   trap - EXIT
   rm -rf "${TEMPDIR}"
   exit ${status}
 }
 trap cleanup EXIT
@@ skipping 60 matching lines @@
     then
       # If there are non-javaplugin.so errors, treat as errors and exit
       echo 'ERRORS: Failed to update alternatives for java-6-sun:'
       grep -v 'javaplugin.so' "${TEMPDIR}"/update-java-alternatives.out
       exit 1
     fi
   fi
 fi
 
 echo "install-build-deps-android.sh complete."