After installing sun-jdk on my computer, every time I run 'emerge --world update' portage wants to install blackdown-jdk and blackdown-jre. QUOTE from /etc/make.profile/virtuals virtual/jdk dev-java/blackdown-jdk virtual/jre dev-java/blackdown-jre END of QUOTE If I change these lines to say dev-java/sun-jdk, portage is happy about my current installation. But this file gets overwritten at each 'emerge rsync'. Is this the intended behaviour of portage for java-installation? Since sun-jdk provides both virtual/jdk and virtual/jre, why does portage want to install blackdown? Not sure if this bug is related to portage itself or the java-ebuilds. Best regards Martin Blix Grydeland
Daniel, don't the latest (masked) Portage version fix this ?
Daniel, reproducing this bug is easy. 1) Remove all JREs and JDKs you have installed. 2) Install the IBM JDK 3) emerge rsync to get the "Offical" virtuals file 4) emerge dev-java/ibm-jdk Now ibm-jdk provides both virtual/jdk-1.3 and virtual/jre-1.3, but when I do emerge --update --world update, portage still wants to install blackdown-jre and blackdown-jdk, even though ibm-jdk already provides the necessary virtuals. Obviously, this is with portage 1.8.8-r1
Hey Karl -- there are several known issues with --world --update, which is why it has been removed and is pending a rewrite before the 1.0 release. If this problem can only be triggered with --world --update, then it's a known issue and will be fixed when Gentoo 1.0 is released (March 31)
This should now be fixed in portage-1.8.9_pre33 (coming soon)
