From: James Le Cuirot <chewi@aura-online.co.uk>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] problems emerging jruby
Date: Sat, 5 Jul 2008 10:59:04 +0100 [thread overview]
Message-ID: <20080705105904.04355be0@symphony> (raw)
In-Reply-To: <486F442E.80803@gentoo.org>
On Sat, 05 Jul 2008 12:51:42 +0300
Petteri Räty <betelgeuse@gentoo.org> wrote:
> Alistair Bush kirjoitti:
> > Chewi, what dependency are we missing?
> >
>
> || ( >=dev-lang/python-2.5 dev-python/celementtree )
> we could even have a fallback for dev-python/elementtree as they
> provide the same API
>
I was just about to post the same thing! It confused me a little at
first because I appeared to have celementtree even though I didn't have
the package installed. This wasn't entirely my fault, Betelgeuse used
celementtree in build-xml-rewrite before I used it in jarjarclean. ;)
--
gentoo-java@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-07-05 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 21:38 [gentoo-java] problems emerging jruby Steven Jenkins
2008-07-05 2:07 ` Alistair Bush
2008-07-05 6:53 ` Fabian Groffen
2008-07-05 7:18 ` Steven Jenkins
2008-07-13 18:09 ` Steven Jenkins
2008-07-05 9:51 ` Petteri Räty
2008-07-05 9:59 ` James Le Cuirot [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=20080705105904.04355be0@symphony \
--to=chewi@aura-online.co.uk \
--cc=gentoo-java@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