New stable version of Android Studio is available on https://developer.android.com/studio Release notes: https://developer.android.com/studio/releases Seems that slight modification of ebuild script might be enough Reproducible: Always
Created attachment 764022 [details] ebuild for dev-util/android-studio-2021.1.1.20 This ebuild seems to work.
Thank you for your contribution. I had a short look on the ebuild. Here a few ideas: * Please test the ebuild with repoman full -d -x https://wiki.gentoo.org/wiki/Repoman and pkgcheck scan --net * We always try to use the latest EAPI, please bump to EAPI=8 * please fix the header. (see /usr/portage/skel.ebuild and https://devmanual.gentoo.org/ebuild-writing/eapi/) * A bot can look for additional mistakes, if you upload a PR via github * unused eclass: eutils
Pull request is waiting for acceptance, but I've also created repository at https://github.com/AdamGiergun/adasss for anyone wanting to try my packages. Apart from package with the latest official release of Android Studio I've created separate packages for beta and canary versions, so they can be installed side by side with official (it's also waiting to be added to the official list of repositories).
As my repository with Android Studio ebuilds is added to repos.gentoo.org I'll keep updating them. It' seems that for minor version bumps there's no need to update ebuild. However it seems that for major version bumps some changes are usually needed. For me it'd be nice if somebody else would check such ebuild. What would be the best way to achieve it?
even newer version is available "Chipmunk | 2021.2.1.xx" https://developer.android.com/studio#downloads
@Rahil I'm afraid that https://github.com/gentoo-mirror/adasss is the only place where it will be possible to find it.
@Adam Giergun thanks for this. I hope it gets merged soon
(In reply to Rahil Bhimjiani from comment #7) > @Adam Giergun thanks for this. I hope it gets merged soon If you mean merging changes from private repos to the main tree don't wait for it. Ebuilds from private repos aren't merged to the Gentoo's main tree in any way. I would have to make a PR (pull request) to the main tree. But looking how long my PR for 2021.1.1.21 https://github.com/gentoo/gentoo/pull/24111 is waiting for review I gave up making PR and started my own repo. So if you want to install latest version of Android Studio go to https://github.com/AdamGiergun/adasss and follow instructions. If you are afraid of using packages from external repos just download https://github.com/AdamGiergun/adasss/blob/master/dev-util/android-studio/android-studio-2021.2.1.14.ebuild and compare with the latest one from the main tree. You should see that there nothing to be afraid of :)
(In reply to Adam Giergun from comment #8) > (In reply to Rahil Bhimjiani from comment #7) > > @Adam Giergun thanks for this. I hope it gets merged soon > > If you mean merging changes from private repos to the main tree don't wait > for it. Ebuilds from private repos aren't merged to the Gentoo's main tree > in any way. > > I would have to make a PR (pull request) to the main tree. But looking how > long my PR for 2021.1.1.21 https://github.com/gentoo/gentoo/pull/24111 is > waiting for review I gave up making PR and started my own repo. > > So if you want to install latest version of Android Studio go to > https://github.com/AdamGiergun/adasss and follow instructions. > > If you are afraid of using packages from external repos just download > https://github.com/AdamGiergun/adasss/blob/master/dev-util/android-studio/ > android-studio-2021.2.1.14.ebuild and compare with the latest one from the > main tree. You should see that there nothing to be afraid of :) Adam, thanks for your work. Great job. I will work to get the non-beta, non-canary ebuild into the tree. It looks like we first should examine the licenses in the tarball and make sure we have them covered. I think we're missing at least one that I saw, I am looking at this now.
(In reply to Mike Pagano from comment #9) > > Adam, thanks for your work. Great job. I will work to get the non-beta, > non-canary ebuild into the tree. > > It looks like we first should examine the licenses in the tarball and make > sure we have them covered. I think we're missing at least one that I saw, I > am looking at this now. Regarding licenses: as Google requires acceptance for "Android Software Development Kit License Agreement" before downloading Android Studio I've added it to my ebuilds. As for other licenses I remember that running Android Studio for the first time one have to accept several licenses.
(In reply to Adam Giergun from comment #10) > (In reply to Mike Pagano from comment #9) > > > > Adam, thanks for your work. Great job. I will work to get the non-beta, > > non-canary ebuild into the tree. > > > > It looks like we first should examine the licenses in the tarball and make > > sure we have them covered. I think we're missing at least one that I saw, I > > am looking at this now. > > Regarding licenses: > > as Google requires acceptance for "Android Software Development Kit License > Agreement" before downloading Android Studio I've added it to my ebuilds. > > As for other licenses I remember that running Android Studio for the first > time one have to accept several licenses. I found at least 2 I don't think we have OROMatcher License ASM Commons Everything else it looks like we have, we just to add them to the ebuild LICENSE="Apache-2.0 android BSD BSD-2 CDDL-1.1 CPL-0.5 EPL-1.0 GPL-2 GPL-2+ JDOM IJG LGPL-2.1 MIT MPL-1.1 MPL-2.0 NPL-1.1 OFL ZLIB"
(In reply to Mike Pagano from comment #11) > (In reply to Adam Giergun from comment #10) > > (In reply to Mike Pagano from comment #9) > > > > > > Adam, thanks for your work. Great job. I will work to get the non-beta, > > > non-canary ebuild into the tree. > > > > > > It looks like we first should examine the licenses in the tarball and make > > > sure we have them covered. I think we're missing at least one that I saw, I > > > am looking at this now. > > > > Regarding licenses: > > > > as Google requires acceptance for "Android Software Development Kit License > > Agreement" before downloading Android Studio I've added it to my ebuilds. > > > > As for other licenses I remember that running Android Studio for the first > > time one have to accept several licenses. > > I found at least 2 I don't think we have > > OROMatcher License > ASM Commons > > Everything else it looks like we have, we just to add them to the ebuild > > LICENSE="Apache-2.0 android BSD BSD-2 CDDL-1.1 CPL-0.5 > EPL-1.0 GPL-2 GPL-2+ JDOM IJG LGPL-2.1 MIT > MPL-1.1 MPL-2.0 NPL-1.1 OFL ZLIB" Sorry for the bug spam. It looks like only OROMatcher is missing
(In reply to Mike Pagano from comment #12) > (In reply to Mike Pagano from comment #11) > > (In reply to Adam Giergun from comment #10) > > > (In reply to Mike Pagano from comment #9) > > > > > > > > Adam, thanks for your work. Great job. I will work to get the non-beta, > > > > non-canary ebuild into the tree. > > > > > > > > It looks like we first should examine the licenses in the tarball and make > > > > sure we have them covered. I think we're missing at least one that I saw, I > > > > am looking at this now. > > > > > > Regarding licenses: > > > > > > as Google requires acceptance for "Android Software Development Kit License > > > Agreement" before downloading Android Studio I've added it to my ebuilds. > > > > > > As for other licenses I remember that running Android Studio for the first > > > time one have to accept several licenses. > > > > I found at least 2 I don't think we have > > > > OROMatcher License > > ASM Commons > > > > Everything else it looks like we have, we just to add them to the ebuild > > > > LICENSE="Apache-2.0 android BSD BSD-2 CDDL-1.1 CPL-0.5 > > EPL-1.0 GPL-2 GPL-2+ JDOM IJG LGPL-2.1 MIT > > MPL-1.1 MPL-2.0 NPL-1.1 OFL ZLIB" > > Sorry for the bug spam. > > It looks like only OROMatcher is missing Ok, we don't need this one, the next thing I see is 32 files causing : Notice: Unresolved soname dependencies Looking at these next. FYI, License is now: LICENSE="Apache-2.0 android BSD BSD-2 CDDL-1.1 CPL-0.5 EPL-1.0 GPL-2 GPL-2+ JDOM IJG LGPL-2.1 MIT MPL-1.1 MPL-2.0 NPL-1.1 OFL ZLIB"
(In reply to Mike Pagano from comment #13) > > Ok, we don't need this one, the next thing I see is 32 files causing : > > Notice: Unresolved soname dependencies > > Looking at these next. > > FYI, License is now: > > LICENSE="Apache-2.0 android BSD BSD-2 CDDL-1.1 CPL-0.5 > EPL-1.0 GPL-2 GPL-2+ JDOM IJG LGPL-2.1 MIT > MPL-1.1 MPL-2.0 NPL-1.1 OFL ZLIB" Most of them regards plugins, and I have suspicion that these dependencies shall be fulfilled not by the system on which Android Studio runs, but by the Android on which an app created with Android Studio is run.
As for me the bigger problem is that a very important part of Android Studio, the qemu based emulator, is installed by Android Studio built-in SDK Manager and thus bypasses any dependency checking. It is possible to build it from sources, but, when I tried it, it took some 60GB or more on disk. It can't be replaced by pure qemu, because it contains many modifications for maintaining Android vms. There is one annoying bug regarding this Android emulator. In the "Extended Controls" of the vm, in the "Location" it should show a map to be able to set a false location for testing. But since some time it stopped doing it, and I have no idea what might be causing it.
(In reply to Adam Giergun from comment #14) > (In reply to Mike Pagano from comment #13) > > > > Ok, we don't need this one, the next thing I see is 32 files causing : > > > > Notice: Unresolved soname dependencies > > > > Looking at these next. > > > > FYI, License is now: > > > > LICENSE="Apache-2.0 android BSD BSD-2 CDDL-1.1 CPL-0.5 > > EPL-1.0 GPL-2 GPL-2+ JDOM IJG LGPL-2.1 MIT > > MPL-1.1 MPL-2.0 NPL-1.1 OFL ZLIB" > > Most of them regards plugins, and I have suspicion that these dependencies > shall be fulfilled not by the system on which Android Studio runs, but by > the Android on which an app created with Android Studio is run. Can you run this executable on your system? /opt/android-studio/plugins/android/resources/installer/x86_64/installer
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=12bf499e31808736578daca3e4a8bb20fbae7fcc commit 12bf499e31808736578daca3e4a8bb20fbae7fcc Author: Mike Pagano <mpagano@gentoo.org> AuthorDate: 2022-05-10 19:36:44 +0000 Commit: Mike Pagano <mpagano@gentoo.org> CommitDate: 2022-05-10 19:38:38 +0000 dev-util/android-studio: add 2021.2.1.14 thanks to Adam Giergun Some changes based on the version made by Adam Giergun. Updated licenses, removed commented lines There are some QA so name concerns we should address but I did not want to delay this release waiting on me. Closes: https://bugs.gentoo.org/832414 Signed-off-by: Mike Pagano <mpagano@gentoo.org> dev-util/android-studio/Manifest | 1 + .../android-studio-2021.2.1.14.ebuild | 116 +++++++++++++++++++++ 2 files changed, 117 insertions(+)
really awesome work, guys! @Adam Giergun, you should apply for Gentoo Developer, or if it's too much then maybe maintain ebuilds in GURU so that more users can benefit.
(In reply to Mike Pagano from comment #16) > > Can you run this executable on your system? > > /opt/android-studio/plugins/android/resources/installer/x86_64/installer Output: There is no such file or directory
(In reply to Rahil Bhimjiani from comment #18) > really awesome work, guys! > @Adam Giergun, you should apply for Gentoo Developer, or if it's too much > then maybe maintain ebuilds in GURU so that more users can benefit. I only do it because I use Android Studio on Gentoo for my daily work. I don't feel like an expert on Gentoo.
(In reply to Adam Giergun from comment #19) > (In reply to Mike Pagano from comment #16) > > > > Can you run this executable on your system? > > > > /opt/android-studio/plugins/android/resources/installer/x86_64/installer > > Output: > There is no such file or directory My assumption is that this executable is to be run on a vm and install an app from given apk file. Google delivers 4 kinds of vms: arm64-v8a armeabi-v7a x86 x86-64 what exactly matches versions of this executable.
(In reply to Adam Giergun from comment #20) > > I only do it because I use Android Studio on Gentoo for my daily work. > I don't feel like an expert on Gentoo. then why not just install it manually? I installed studio back in 2020 from official site, it was easy. Then it has been updating itself via patches to latest
(In reply to Rahil Bhimjiani from comment #22) > (In reply to Adam Giergun from comment #20) > > then why not just install it manually? I installed studio back in 2020 from > official site, it was easy. Then it has been updating itself via patches to > latest I know that it's possible to do it this way. This approach fails miserably when some new dependency requirement appears.
