# emerge --sync # emerge -uDpv world These are the packages that would be merged, in order: Calculating world dependencies - !!! All ebuilds that could satisfy "=virtual/jdk-1.4*" have been masked. !!! One of the following masked packages is required to complete your request: - virtual/jdk-1.4.2 (masked by: package.mask) - virtual/jdk-1.4.1 (masked by: package.mask) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. !!! Problem resolving dependencies for app-office/openoffice-bin !!! Depgraph creation failed. I've been using this for quite some time w/ dev-java/sun-jre-bin-1.5 only. Sorry, not able to track which eclass did trigger this out of the blue, but I don't want it and it's not needed. This system have USE="-java" and I'm only using JRE for browser plugins and OO.org. Besides, the ebuild directly contradicts the eclass dependencies: <snip> java? ( !amd64? ( >=virtual/jre-1.4 ) amd64? ( app-emulation/emul-linux-x86-java ) ) </snip> Plz. fix this bad dependency instead of forcing people to stick stuff into package.provided, thanks.
Sorry, OO.org folks. This has nothing to do w/ you. java-wm-2.eclass now depends on java-config-1* which in turn PDEPENDs on virtual-jdk-1.4*; there's absolutely no way to have a JRE-only system for people that don't need any JDK now. Java folks, stop punishing users that have some clue just because some users plain can't be bothered to RTFM and keep on trying to compile stuff against JREs, trying to set JRE as their system VM or whatever. That's what INVALID resolution is for. I have no need for JDK on this system, all I need is the latest and greatest JRE to run a bunch of apps. I don't compile anything against Java, don't force it on me. Thanks.
Maybe we could control that PDEPEND in java-config by some "nojdk" USE flag to satisfy both noobs and smart users?
Here is the solution I see: For VMs that we support being used with java-config-1, we add JAVA_SUPPORTS_GENERATION_1 to the ebuild before the inherit. This only includes 1.3 and 1.4 JDKs. In java-vm-2.eclass, we always depend on java-config-2. If we support generation-1, then we also depend on java-config-1. java-config-1 will continue to pull in a 1.4 or 1.3 JDK, because if you're using something that needs it, ie generation-1 ebuild, you WILL need a 1.4 or 1.3 JDK installed. So, if you just install say sun-jre-bin, this will only pull in java-config-2... and things will work as expected. If you go to emerge something built with java, a JDK would get pulled in as normal. If you go to emerge something using generation-1, java-config-1 would get pulled in, and a 1.4 JDK would get pulled if you didn't already have it. This should make everyone happy...
I implemented the solution mentioned in my previous comment. All should be well now.
Yay, unmerged java-config-1*, and all is good now. Thanks! ;)
