From: Vlastimil Babka <caster@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] Virtual troubles
Date: Sat, 12 Jan 2008 18:21:56 +0100 [thread overview]
Message-ID: <4788F734.1020606@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Discovered some problems with virtuals today.
First one is in the depend-java-query tool, which can't correctly parse
dependencies as =java-virtuals/servlet-api-2.3* - transforms to
"servlet-api-2.3*" which it can't find, and raises exception - see how
it ends up in bug 205453 :) So, only deps like
"~java-virtuals/servlet-api-2.3" work. Should be fixed, or we decide to
go with slot deps and start sticking EAPI=1 in our ebuilds? I'm not sure
it can even parse 'java-virtuals/servlet-api:2.3' in current version :)
The other trouble I have is with eclass functions. It's confusing that
java-pkg_getjars() doesn't have --virtual parameter, but if you look
into what the parameter does, you realize it really doesn't need it.
Still, confusing :)
The worse trouble is with the functions that actually take the
parameter, java-pkg_jar-from $package $jar and java-pkg_getjar. By
passing --virtual, you say "I can't know what the particular provider's
jar names are, so depend on the whole package", but still you have to
pass an actual 'foo.jar' parameter. That's strange. What if there's new
provider with different jar name? What if the virtual is satisfied by
the VM itself? Suddenly you get an error, or am I wrong?
VB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkeI9zIACgkQtbrAj05h3oQy/wCfYfxKH7bV3DD7BTaTK3rg3r9o
JGgAn18nsjKZBebQUyi+tfK5vwYa9PbM
=tEpu
-----END PGP SIGNATURE-----
--
gentoo-java@lists.gentoo.org mailing list
next reply other threads:[~2008-01-12 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 17:21 Vlastimil Babka [this message]
2008-01-14 10:27 ` [gentoo-java] Virtual troubles Alistair Bush
2008-01-14 11:06 ` Vlastimil Babka
2008-01-14 11:24 ` Alistair Bush
2008-01-15 13:05 ` Andrew Cowie
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=4788F734.1020606@gentoo.org \
--to=caster@gentoo.org \
--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