Summary: | commons-digester-1.7 requires commons-beanutils | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rabbe Fogelholm <rabbe> |
Component: | New packages | Assignee: | Java team <java> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rabbe Fogelholm
2006-07-04 01:57:35 UTC
From commons-digester-1.7.ebuild: RDEPEND=">=virtual/jre-1.4 =dev-java/commons-beanutils-1.6* >=dev-java/commons-collections-2.1 >=dev-java/commons-logging-1.0.2" DEPEND=">=virtual/jdk-1.4 >=dev-java/ant-core-1.4 junit? ( >=dev-java/junit-3.7 ) jikes? ( dev-java/jikes ) source? ( app-arch/zip ) ${RDEPEND}" It has dev-java/commons-beanutils in {R,}DEPEND. dev-java/commons-beanutils is on the RDEPEND list of the commons-digester-1.7.ebuild. But shouldn't it be on the DEPEND list instead, since it is apparently needed already at emerge time? The same reasoning goes for this bug: http://bugs.gentoo.org/show_bug.cgi?id=139137 Please note that DEPEND has in last line ${RDEPEND}, so it contains all atoms from RDEPEND. > Please note that DEPEND has in last line ${RDEPEND},
> so it contains all atoms from RDEPEND.
I didn't realize that, thank for pointing it out.
But why is it then that commons-beanutils is not emerged automatically? Can we really consider this problem resolved?
Make sure you have the most recent revision of =dev-java/commons-beanutils-1.6* . IIRC correctly, it was slot 0 at some point, and moved to slot 1.6. This required a revision bump. Basically, that atom is trying to get around lack of a SLOT based dependency. So, if you had a revision of 1.6 that was slot 0, it would fill the dependency, but java-pkg_jar-from wouldn't be able to find it at the right slot. |