| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi, |
| 5 |
|
| 6 |
Discovered some problems with virtuals today. |
| 7 |
|
| 8 |
First one is in the depend-java-query tool, which can't correctly parse |
| 9 |
dependencies as =java-virtuals/servlet-api-2.3* - transforms to |
| 10 |
"servlet-api-2.3*" which it can't find, and raises exception - see how |
| 11 |
it ends up in bug 205453 :) So, only deps like |
| 12 |
"~java-virtuals/servlet-api-2.3" work. Should be fixed, or we decide to |
| 13 |
go with slot deps and start sticking EAPI=1 in our ebuilds? I'm not sure |
| 14 |
it can even parse 'java-virtuals/servlet-api:2.3' in current version :) |
| 15 |
|
| 16 |
The other trouble I have is with eclass functions. It's confusing that |
| 17 |
java-pkg_getjars() doesn't have --virtual parameter, but if you look |
| 18 |
into what the parameter does, you realize it really doesn't need it. |
| 19 |
Still, confusing :) |
| 20 |
The worse trouble is with the functions that actually take the |
| 21 |
parameter, java-pkg_jar-from $package $jar and java-pkg_getjar. By |
| 22 |
passing --virtual, you say "I can't know what the particular provider's |
| 23 |
jar names are, so depend on the whole package", but still you have to |
| 24 |
pass an actual 'foo.jar' parameter. That's strange. What if there's new |
| 25 |
provider with different jar name? What if the virtual is satisfied by |
| 26 |
the VM itself? Suddenly you get an error, or am I wrong? |
| 27 |
|
| 28 |
VB |
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v2.0.8 (GNU/Linux) |
| 31 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 32 |
|
| 33 |
iEYEARECAAYFAkeI9zIACgkQtbrAj05h3oQy/wCfYfxKH7bV3DD7BTaTK3rg3r9o |
| 34 |
JGgAn18nsjKZBebQUyi+tfK5vwYa9PbM |
| 35 |
=tEpu |
| 36 |
-----END PGP SIGNATURE----- |
| 37 |
-- |
| 38 |
gentoo-java@l.g.o mailing list |
Archives