From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Android SDK
Date: Fri, 8 Oct 2010 01:07:35 +0200 [thread overview]
Message-ID: <201010080107.35671.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <6035.59999.qm@web51906.mail.re2.yahoo.com>
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
prev parent reply other threads:[~2010-10-07 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 22:49 [gentoo-user] Android SDK BRM
2010-10-07 23:07 ` Alan McKinnon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201010080107.35671.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox