First steps for creating build/install-build-deps.py

First steps for creating build/install-build-deps.py

Supports just --quick-check for now.

BUG=508895
R=jochen@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/2d99f9f5081bcb45a65051b669c689ab673a0200

[Paweł Hajdan Jr., 2015-07-10 15:27:01]

phajdan.jr@chromium.org changed reviewers:
+ jochen@chromium.org

[Paweł Hajdan Jr., 2015-07-10 15:27:02]

See bug for context, but I'm happy to explain more if you'd like.

I intend install-build-deps.sh to eventually just call the .py script.

[jochen (gone - plz use gerrit), 2015-07-13 08:55:09]

lgtm

[Paweł Hajdan Jr., 2015-07-13 09:54:00]

Committed patchset #1 (id:1) manually as
2d99f9f5081bcb45a65051b669c689ab673a0200 (presubmit successful).

[kjellander_chromium, 2015-12-02 10:29:23]

On 2015/07/13 09:54:00, Paweł Hajdan Jr. wrote:
> Committed patchset #1 (id:1) manually as
> 2d99f9f5081bcb45a65051b669c689ab673a0200 (presubmit successful).

I totally support getting rid of the shell script (although with the recent
switch over to using a sysroot image the need of the script is no longer as big,
I guess?).

However, a member of our team today ran into a compilation error due to the
recently added libffi-dev library being missing. She accidentally ran this
script instead of the .sh version, thinking it would fix it (but obviously it
didn't).
Can we either move this script to another location during development, to avoid
confusion, or at least add a large warning when you run the script?