Bug 210432 – new ebuild: google android sdk

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Guilherme Amadio 2008-02-17 03:43:38 UTC]

I'm submitting an ebuild for android-sdk from the Open Handset Alliance, for the
people who want to play with it or maybe participate in the challenge.

from http://code.google.com/android :
Android is a software stack for mobile devices that includes an operating system, middleware and key applications. The Android SDK provides the tools and APIs necessary to begin developing applications on the Android platform using the Java programming language.

[Comment 1 Guilherme Amadio 2008-02-17 03:46:23 UTC]

Created attachment 143718 [details]
android-sdk-5_rc14.ebuild

still don't quite know the best category. dev-embedded or app-mobilephone

[Comment 2 Guilherme Amadio 2008-06-28 04:11:09 UTC]

Created attachment 158721 [details]
android-sdk-5_rc15.ebuild

This ebuild for android-sdk-5_rc15 fixes an issue with the 'doc' use flag.

[Comment 3 Alin Năstac (RETIRED) 2008-07-01 19:04:10 UTC]

This is an SDK, dev-embedded category makes more sense than app-mobilephone.

[Comment 4 Pascal Hartig 2008-08-19 12:34:28 UTC]

Created attachment 163296 [details]
ebuild for 0.9_beta

Changed the naming scheme

[Comment 5 Alexander Glyzov 2008-09-23 21:19:37 UTC]

Created attachment 166203 [details]
an ebuild for the newest android-sdk 1.0 R1

based on the android-sdk-0.9_beta

[Comment 6 Cyrill Helg 2008-09-26 13:53:25 UTC]

is this ebuild in any overlay?

[Comment 7 JTRiley 2008-11-22 20:21:21 UTC]

Works for me on amd64 ~jtriley

[Comment 8 Krzysztof Pawlik (RETIRED) 2009-01-17 12:55:27 UTC]

Alin: as it contains SDK, emulator and other android related tools I'm leaning towards dev-util/android-sdk -- any comments, suggestions anybody?

[Comment 9 Richard Freeman 2009-01-17 13:01:15 UTC]

Created attachment 178784 [details]
Updated to sdk r2, fixed version to match gentoo conventions.

I updated this for the latest sdk, and I also fixed the version numbering (we can't use the gentoo -r# to track an upstream version number).  For now I just hardcoded in the version in MY_P - it isn't entirely clear that their version numbering is completely stable at this point looking at past releases.

I'd be interested in feedback about the new ebuild.  I'm considering maintaining this in portage.  I have a G1, and I'm interested in tinkering with it, but I'm not going to be a serious android developer so I'll be interested in feedback from those who are.

[Comment 10 Cyrill Helg 2009-01-17 13:12:30 UTC]

Thanks, works without problems here.

[Comment 11 Krzysztof Pawlik (RETIRED) 2009-01-17 13:19:09 UTC]

Created attachment 178788 [details]
android-sdk-1.0_p2.ebuild

Instead of 1.0.2 I suggest 1.0_p2 -- that way when 1.0.1 comes out we won't have any problems with it. Also: added examples USE flag, moved tools/NOTICE.txt to /usr/share/doc/...

[Comment 12 Krzysztof Pawlik (RETIRED) 2009-01-17 13:24:22 UTC]

Created attachment 178789 [details]
android-sdk-1.0_p2.ebuild

Improved version: installs to /opt/android-sdk-1.0/

[Comment 13 Richard Freeman 2009-01-17 14:55:23 UTC]

Ok, this is now in portage.  We're going to co-maintain so let either of us know if there are any issues.

[Comment 14 Claudio Roberto França Pereira 2011-05-28 04:35:03 UTC]

I'm having permission problems basically with /opt/android-sdk-update-manager/tools folder. The app is trying to rename the tools folder to temp/sometmpname while updating its tools. I've modified my sdk folder, gave ownership to my main user (my main user is already on the android group) and tweaked some permission flags (I had this issue before and had to give almost full permission to everyone to fix it), but now I'd like to know if people are using the ebuild without any problems.

I'd like to reset permissions and ownership, what is the best approach? Backup platform files and reinstall the sdk-manager ebuild?

[Comment 15 Richard Freeman 2011-05-28 14:37:58 UTC]

(In reply to comment #14)
> I'm having permission problems basically with
> /opt/android-sdk-update-manager/tools folder. The app is trying to rename the
> tools folder to temp/sometmpname while updating its tools. I've modified my sdk
> folder, gave ownership to my main user (my main user is already on the android
> group) and tweaked some permission flags (I had this issue before and had to
> give almost full permission to everyone to fix it), but now I'd like to know if
> people are using the ebuild without any problems.
> 
> I'd like to reset permissions and ownership, what is the best approach? Backup
> platform files and reinstall the sdk-manager ebuild?

Bugs are not the best way to ask for help - better to ask on forums/lists.  

You do need to be in the android group per the ebuild notices to use the installer - I haven't had these issues and just tested it out a few days ago.  

If you've messed around with permissions your best bet is probably to just delete the entire android directory tree under /opt, and then just emerge the package again.  Simply un-merging the package will leave behind any files that the installer downloaded, and any permissions issues that created.

[Comment 16 Claudio Roberto França Pereira 2011-05-28 15:14:17 UTC]

Ok, sorry about that. I thought maybe the bug wasn't fully resolved yet. I'll try again from scratch, if anything arises, I'll report as a new bug.