Created attachment 504126 [details] android-sdk-update-manager-3859397.ebuild android-sdk-manager seems not be receiving further updates. It seems google would prefer people to use android-studio for updating their tools, which is a little bit heavy for most purposes. Luckily, they also provide a package containing command-line tools to work with the same packages. The latest version can be found at: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip Updating the android-sdk-update-manager ebuild is reasonably straight forward (the sdk-tools-linux zip effectively just contains the tools directory from the original android-sdk-update-manager package). I couldn't figure out whether the tools/lib/monitor-x86* files were necessary, but otherwise it's close to a straight copy (with potentially some path updates). I've attached a hastily hacked together proof-of-concept that is NOT supposed to be the finished version, but is to provide an idea of the changes that might be necessary. Please let me know if you think this is a reasonable idea? I'm happy to help with testing or anything else that might be necessary... 5:)
Thanks for the ebuild it works nicely here!, after getting almost crazy for a day trying to make the jenkins android emulator plugin work on my Gentoo server, I realized the current ebuild is not up to date, completely breaking the jenkins plugin.
(In reply to Mike Auty from comment #0) > Created attachment 504126 [details] > android-sdk-update-manager-3859397.ebuild > > android-sdk-manager seems not be receiving further updates. It seems google > would prefer people to use android-studio for updating their tools, which is > a little bit heavy for most purposes. > > Luckily, they also provide a package containing command-line tools to work > with the same packages. The latest version can be found at: > > https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip > > Updating the android-sdk-update-manager ebuild is reasonably straight > forward (the sdk-tools-linux zip effectively just contains the tools > directory from the original android-sdk-update-manager package). I couldn't > figure out whether the tools/lib/monitor-x86* files were necessary, but > otherwise it's close to a straight copy (with potentially some path > updates). I've attached a hastily hacked together proof-of-concept that is > NOT supposed to be the finished version, but is to provide an idea of the > changes that might be necessary. > > Please let me know if you think this is a reasonable idea? I'm happy to > help with testing or anything else that might be necessary... 5:) Perhaps we should rename this package to dev-util/android-sdk[-tools] then? I don't think the name still fits. Also, I have created a separate package for the commandline tools from Android Studio, (See: https://gitlab.com/oxr463/overlay/-/tree/master/dev-util/android-commandlinetools-bin).
I tried to use `fastboot` from dev-util/android-tools-9.0.0_p3-r1, but when executing `fastboot devices` while an Android phone in fastboot mode is connected, I get the following error message: ``` no permissions (user in plugdev group; are your udev rules wrong?); see [http://developer.android.com/tools/device.html] fastboot ``` Following that link (it now redirects to [1]) and also looking into Gentoo bug #491508, understood that in the past these Udev rules were provided by the Android SDK tools [2] that Gentoo packages as dev-util/android-sdk-update-manager. I also figured out (from the same link [2]) that these SDK tools are no longer maintained and are superseded by the Android Studio Command Line Tools [3], which appear to be what this bug is about. Now I wonder whether installing these tools would solve my problem of installing the missing Udev rules, since from comment #0 it appears that they only include tools and from a quick look at commandlinetools-linux-7302050_latest.zip it appears that indeed there are no Udev rules files inside. So my question is: Where do I get the missing Udev rules from? Will the changes proposed in this bug here solve my problem? [1]: https://developer.android.com/studio/run/device [2]: https://developer.android.com/studio/releases/sdk-tools [3]: https://developer.android.com/studio#cmdline-tools
