Package Details: android-sdk-platform-tools 35.0.1-1

Git Clone URL: https://aur.archlinux.org/android-sdk-platform-tools.git (read-only, click to copy)
Package Base: android-sdk-platform-tools
Description: Platform-Tools for Google Android SDK (adb and fastboot)
Upstream URL: http://developer.android.com/sdk/index.html
Keywords: android development
Licenses: custom
Conflicts: adb
Provides: adb, android-tools
Submitter: Gordin
Maintainer: dreamingincode
Last Packager: dreamingincode
Votes: 1271
Popularity: 2.59
First Submitted: 2011-01-29 23:08 (UTC)
Last Updated: 2024-03-23 00:54 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 19 Next › Last »

chrbayer commented on 2016-05-21 17:00 (UTC)

Thank you very much for pointing this out, I changed the post_install to simple inform the user to source /etc/profile on its own.

grawity commented on 2016-05-21 16:06 (UTC)

That install scripts run as root isn't the problem – the problem is that environment doesn't magically propagate 'upwards'. You have something like this: bash (user) └─makepkg -i ··└─sudo pacman… ····└─pacman -U android-etc.pkg.tar.xz ······└─sh -c ". /tmp/pacman/android-etc.install && post_install" Changing PATH from post_install only affects that last 'sh' process, not any 'above' processes.

yan12125 commented on 2016-05-21 13:35 (UTC)

Don't add `source` commands to install scripts. Install scripts are run as root and a `source` command in these scripts does not make sense. And I don't think PKGBUILD can change users' environment. What *.install should do is just asking users to relogin or reopen the terminal, just like what android-sdk does. [1] [1] https://aur.archlinux.org/cgit/aur.git/tree/android-sdk.install?h=android-sdk

duttondj commented on 2016-03-17 15:22 (UTC) (edited on 2016-03-17 15:23 (UTC) by duttondj)

The PKGBUILD should run: source /etc/profile.d/android-sdk-platform-tools.sh source /etc/profile.d/android-sdk-platform-tools.csh That should allow you to run adb immediately after install. Otherwise, you would just have to open a new terminal.

chrbayer commented on 2016-03-13 11:45 (UTC)

what do you mean with not able to run adb? Can you provide some logging data?

physicalit commented on 2016-03-13 11:21 (UTC)

not being able to run "adb" after install should be considered a real bug for this package.

isfeldt34 commented on 2016-03-12 12:28 (UTC)

works just fine changing the line arch=x86_64 to arch=i686. since this is a 32Bit machine, other than that, all is well! and adb works as well here.

thx1138 commented on 2016-03-07 01:10 (UTC)

> Wouldn't it be useful to reload /etc/profile at the end of the PKGBUILD > or redefining the PATH ? This is a problem with the default "filesystem 2015.09-1" package, where "/etc/profile" sets "/usr/bin" in PATH="/usr/local/sbin:/usr/local/bin:/usr/bin" *before* including from "/etc/profile.d/". You can edit /etc/profile, removing "/usr/bin", and then, *after* "# Load profiles..." add export PATH=$PATH:/usr/bin It seems a bit odd though, having the overlap with the community/android-tools package, and installing android-sdk-platform-tools in /opt.

Munto commented on 2016-01-17 02:28 (UTC)

Hi. Thank you for your package. I just installed it but I was a little bit disturbed right after because the command `adb` wasn't available. I had to recheck the PKGBUILD to see what was done exactly. Wouldn't it be useful to reload /etc/profile at the end of the PKGBUILD or redefining the PATH ?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 19 Next › Last »