Hi, at the moment, only commons-daemon-1.0.1 (without r1) is stable (x86) and it depends on >=virtual/jdk-1.4. But virtual/jdk-1.5 is stable already, and commons-daemon-1.0.1 does not compile with jdk 1.5 - only with 1.4 and below. So commons-daemon-1.0.1-r1 compiles fine with jdk 1.5, so it should be marked stable to resolve the issue. Thanks.
Your reasoning is wrong, depend on >=virtual/jdk-1.4 doesn't mean much with gen-1 ebuild which are locked to 1.4 JDK for building. There's no issue here. Anyway, it's old enough to get stable and punt another gen-1 ebuild away, so please do.
(In reply to comment #1) > Your reasoning is wrong, depend on >=virtual/jdk-1.4 doesn't mean much with > gen-1 ebuild which are locked to 1.4 JDK for building. There's no issue here. I wish it was ... but "emerge -uD commons-daemon -p" doesn't pull in any 1.4 JDK - it does not even pull in virtual/jdk-1.4 ... Well, commons-daemon complains about a missing gen-1 JDK, when i try to compile it. But that's it.
(In reply to comment #2) > (In reply to comment #1) > > Your reasoning is wrong, depend on >=virtual/jdk-1.4 doesn't mean much with > > gen-1 ebuild which are locked to 1.4 JDK for building. There's no issue here. > > I wish it was ... > > but "emerge -uD commons-daemon -p" doesn't pull in any 1.4 JDK - it does not > even pull in virtual/jdk-1.4 ... > > Well, commons-daemon complains about a missing gen-1 JDK, when i try to compile > it. But that's it. > We could not depend on a JDK in gen 1 because of 137971
(In reply to comment #3) > > We could not depend on a JDK in gen 1 because of 137971 > That might not be related. Well commons-daemon does have the atoms so I fail to see the point, but let's get gen 2 stable as it is better all around. DEPEND=">=virtual/jdk-1.4 dev-java/ant-core jikes? ( dev-java/jikes ) source? ( app-arch/zip )" RDEPEND=">=virtual/jre-1.4"
x86 stable
ppc stable
ppc64 stable
amd64 stable
