1 |
For bug 118651 [1], the user was experiencing problems with binary |
2 |
packages because java-config is in DEPEND, not RDEPEND, which wouldn't |
3 |
be brought in as a dependency for a binary install. |
4 |
|
5 |
The user had suggested putting this in the particular ebuild's RDEPEND. |
6 |
However, this would affect all JDKs and JREs. So instead, I propose |
7 |
putting java-config in DEPEND and RDEPEND of java.eclass, which all JDKs |
8 |
and JREs should be inheriting. The ebuilds would then need to be updated |
9 |
to not DEPEND on java-config. |
10 |
|
11 |
Would there be any problem with doing this? If not, is there a minimal |
12 |
version of java-config that should be used? sun-jdk depends on >= 1.2, |
13 |
ibm-jdk-bin depends on >= 0.2.5, and blackdown-jdk depends on >= 1.2.11, |
14 |
so I'm not sure which one should be used. |
15 |
|
16 |
- Josh |
17 |
-- |
18 |
gentoo-java@g.o mailing list |