Package Details: depot-tools-git r9435.249e9a26c-1

Git Clone URL: https://aur.archlinux.org/depot-tools-git.git (read-only, click to copy)
Package Base: depot-tools-git
Description: Tools for working with Chromium development
Upstream URL: https://chromium.googlesource.com/chromium/tools/depot_tools
Keywords: chromium depot_tools google
Licenses: custom
Submitter: aperez
Maintainer: alerque
Last Packager: alerque
Votes: 87
Popularity: 0.000007
First Submitted: 2014-07-07 14:25 (UTC)
Last Updated: 2024-03-27 09:21 (UTC)

Dependencies (4)

Sources (1)

Pinned Comments

alerque commented on 2021-09-23 08:19 (UTC)

Installers beware! This package is a fiasco and the upstream Git repository basically has bunch of binary blobs in it that do strange things. I'm working on cleaning up the packaging some but the upstream behavior is egregious. Wash your /opt/depot_tools directory out with soap and bleach when done.

relrel commented on 2020-10-30 11:30 (UTC)

depot_tools is installed in /opt/depot_tools/. This directory is not in $PATH by default, so make sure to export PATH=/opt/depot_tools:$PATH before using it. Also, this directory has root permissions, so either use it as root, or if you want to use it as your currect user:

# groupadd depot_tools
# gpasswd -a $(whoami) depot_tools
# setfacl -m g:depot_tools:rwX /opt/depot_tools/

Then re-login as your current user or log your terminal in to the newly created group:

$ newgrp depot_tools

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

watermelonjuice commented on 2016-06-01 23:17 (UTC) (edited on 2016-06-01 23:18 (UTC) by watermelonjuice)

Build fails +1

jro commented on 2016-06-01 20:52 (UTC)

build fails: Checking connectivity... done. -> Found depot_tools.sh -> Found repo_fix.sh -> Found fixshebangs.py ==> Validating source files with sha512sums... depot-tools-git ... Skipped depot_tools.sh ... Passed repo_fix.sh ... Passed fixshebangs.py ... Passed ==> Extracting sources... -> Creating working copy of depot_tools git repo... Cloning into 'depot-tools-git'... done. ==> Starting prepare()... ==> Patching scripts for python2 usage... sed: can't read hammer: No such file or directory ==> ERROR: A failure occurred in prepare(). Aborting... ==> ERROR: Makepkg was unable to build depot-tools-git. ==> Restart building depot-tools-git ? [y/N] ==> ---------------------------------------- ==>

sleeping commented on 2016-03-08 10:19 (UTC)

Beware that this should be installed in a directory ending with depot_tools to be able to install V8, they hardcoded that in the source (God knows why) https://chromium.googlesource.com/v8/v8/+/roll/build/download_gold_plugin.py Alternatively, create a symlink.

AWhetter commented on 2015-10-30 21:15 (UTC)

As a bit of a quick and dirty way of doing the python2 substitutions I used the following: for i in $(find -type f -not -path .git); do sed -i -e '1s/env python$/env python2/' -e 's/exec python /exec python2 /' -e 's/^python /python2 /' $i; done

aperez commented on 2015-07-23 12:32 (UTC)

@ausbin: Yeah, you are right: the fixed list of scripts in which to edit shebangs is quite annoying to maintain. In the end I have made a quick Python script which will edit them only in the first line, and only for scripts which already had a shebang beforehand. This is now run from the “prepare()” function. Also, notice how I had to leave still some fixing to “sed” because there are some shell scripts which do “exec python ...”, and those have to be changed to “exec python2 ...”. The latter are just a few, and quite unlikely to change, so I have opted for keeping a static list for those.

ausbin commented on 2015-07-18 21:23 (UTC)

Hey, thanks a bunch for this package. It's saved me a lot of time. I think your hard-coded list of scripts is out of date, though. (it missed a few shebangs for me, at least). Instead of fixing the list every time the scripts shuffle around in git, maybe you could try something like the following: http://ix.io/jOw. It just replaces every instance of the wrong (python 3) shebang with the right (python 2) one. It ain't pretty -- it replaces *all* matching lines, not just the first -- but it works. As a side note to future readers: in general, I'd suggest against following stubb's suggestion of symlinking /usr/bin/python to /usr/bin/python2. Sure, it'll work, but you run the risk of breaking scripts such as youtube-dl that (correctly) expect /usr/bin/python to be Python 3. Simply replacing the bad shebangs in the package you're building avoids such issues and doesn't prevent you from installing Python 3 later.

twelveeighty commented on 2014-12-06 13:52 (UTC)

@stubb, okay, I'll try that instead of the repo_fix script. Thanks!

stubb commented on 2014-12-01 23:46 (UTC)

@twelveeighty Looks like you missed that simply symlink trick https://wiki.archlinux.org/index.php/Python#Python_2

twelveeighty commented on 2014-12-01 16:12 (UTC)

Folks, I need some pointers. I'm using depot-tools to build mod_pagespeed. I keep getting the Python 3 vs. 2 problem (error code below), so I'm sure I'm missing something that has to be fixed with that repo_fix.sh script included in this package. But, I can't seem to find the folder that I need to run that script against. There's no ".repo" folder I can find? ________ running '/usr/bin/python2 src/build/gyp_chromium -Dchromium_revision=256281' in '/mnt/encrypted/data/twelveeighty/work/builds/mod_pagespeed' Updating projects from gyp files... File "../build/linux/detect_host_arch.py", line 31 print host_arch ^ SyntaxError: Missing parentheses in call to 'print' gyp: Call to 'python ../build/linux/detect_host_arch.py' returned exit status 1.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »