Package Details: android-sdk 26.1.1-2

Git Clone URL: https://aur.archlinux.org/android-sdk.git (read-only, click to copy)
Package Base: android-sdk
Description: Google Android SDK
Upstream URL: https://developer.android.com/studio/releases/sdk-tools.html
Keywords: android development
Licenses: custom
Submitter: None
Maintainer: dreamingincode
Last Packager: dreamingincode
Votes: 1479
Popularity: 0.163656
First Submitted: 2007-11-12 19:26 (UTC)
Last Updated: 2022-03-22 20:58 (UTC)

Dependencies (22)

Sources (5)

Pinned Comments

dreamingincode commented on 2020-03-11 07:51 (UTC) (edited on 2020-03-11 08:50 (UTC) by dreamingincode)

@benedikt

cmdline-tools should be a different package because it's installed at android-sdk/cmdline-tools/latest, not android-sdk/tools of this package. They show up as different packages in Android Studio SDK manager as well, and they can be installed side-by-side.

Update: The new package has been published at https://aur.archlinux.org/packages/android-sdk-cmdline-tools-latest/

dreamingincode commented on 2017-04-18 11:40 (UTC) (edited on 2017-04-19 07:28 (UTC) by dreamingincode)

I'm going to update this package to 26.0.1 (it has been long-outdated), according to https://dl.google.com/android/repository/repository2-1.xml which is used by Android Studio. Some tools have been removed by upstream in this update (namely the standalone SDK Manager's GUI), and you may want to check against https://developer.android.com/studio/releases/sdk-tools.html for the breaking changes before this update. If you are using an AUR helper and you want to stay on the old version, consult your AUR helper's manual.

Latest Comments

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 44 Next › Last »

Nothing4You commented on 2014-05-01 21:10 (UTC)

Ugh sorry, didn't read comments before flagging. Is there a way to see which version is contained in the tarball before downloading it?

<deleted-account> commented on 2014-05-01 16:21 (UTC)

Updated PKGBUILD: http://pastebin.com/raw.php?i=JwfuDx0i Uses http://dl-ssl.google.com/android/repository/repository-8.xml as source, which is what the "android" command line tool uses. Use sha1sums since that is what is provided by Google in the xml file.

thestinger commented on 2014-05-01 05:25 (UTC)

Again, please don't flag this out-of-date before there's a new tarball. The out-of-date flag is for informing the packager when upstream has officially released a new version. It's not relevant if they're rolling it out via their updater, unless someone wants to suggest a different source than <https://developer.android.com/sdk/index.html>.

thestinger commented on 2014-04-30 02:48 (UTC)

There's no point in flagging it out-of-date before a new tarball is released.

<deleted-account> commented on 2014-03-29 21:38 (UTC)

Updated PKGBUILD for 22.6.2: http://pastebin.com/raw.php?i=wiNZJ0T6 Switched to md5sums because Google provides an official md5sum for the tools package at https://developer.android.com/sdk/index.html

<deleted-account> commented on 2014-03-26 22:44 (UTC)

22.6.2 has been released

thestinger commented on 2014-03-12 18:59 (UTC)

I could make all the dependencies optional, but I don't plan to do it. Arch is the wrong distribution to use if you care about disk space usage.

danyf90 commented on 2014-03-11 21:15 (UTC)

hi, isn't swt just an optional dependency (needed only if you need GUI)?

thestinger commented on 2014-03-07 05:01 (UTC)

Regardless of what an unprotected page on a collaboratively edited document recommends, it's not something that's supported by this package. I can't really see why anyone would be using this package if they just plan on overwriting the files with updates from `android`. Just install it to your home directory and don't run that brittle tool as root or mess with files you've asked the system package manager to manage. There are really not a lot of extra packages, and maintaining Arch packages for them is entirely realistic. In fact, I think there are already up-to-date packages for nearly all of them. If one of them is not being maintained well, just let me know and I'll orphan it. I'll consider leaving out the package management tool in future updates, to make this clearer.

ackalker commented on 2014-03-07 03:57 (UTC)

Well, installing just the core components, then using `android` to install the API etc., is precisely what the Arch Linux Wiki recommends: https://wiki.archlinux.org/index.php/Android#Install_Android_SDK_core_components https://wiki.archlinux.org/index.php/Android#Getting_Android_SDK_platform_API As I've said before, I utterly dislike the idea of having to run `android` as root to install extra components, but I (and I presume the Wiki editor(s)) have tried many, many other ways, but failed. Also, the 'net is awash with postings from people who have similar problems, and who in the very end settle for the same solution. I've had similar problems with Eclipse for many years, until the Eclipse devs (probably under pressure from users of major distros like Debian&co) fixed things so that users could install Eclipse system-wide, then add components per-user. If we give in and plonk SDKs in our home directories, etc. I don't think we're giving Google a clear enough signal to go change their ways. IMHO.

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 44 Next › Last »