Apparently, though unproven, at 00:49 on Friday 08 October 2010, BRM did opine 
thusly:

> I noticed there have been a few Android SDK's in portage now for a while -
> originally android-sdk, now android-sdk-update-manager
> (http://packages.gentoo.org/package/dev-util/android-sdk-update-manager).
> I know there is a bug on it - http://bugs.gentoo.org/show_bug.cgi?id=320407
> - but that's the only one I can find.
> 
> Anyone have an idea on when some version might go stable?
> There's 7 versions in portage and all are testing; the first (version 3)
> goes back to November 2009.


You should file a stabilisation request at b.g.o. they are likely not in 
testing because there's something wrong with them, they are probably in 
testing because nobody has bothered bumping them to stable.

However, considering the speed that Google are releasing Android versions, I 
think that the usual gentoo arch/~arch methodology is a bit of a joke in this 
case. If you didn't use the ebuilds, you'd be installing the latest sdk from 
google anyway, right? All the ebuild does is unpack a binary archive into 
/opt, nothing magic there, no real compelling need to wait for a stable 
version. And it doesn't need any ~arch deps either

I say just be done with it, keyword the damn thing and install it.


-- 
alan dot mckinnon at gmail dot com

Reply via email to