On re-emerging sun-jdk and blackdown-jdk I ended up with an empty /etc/env.d/java folder. At the end of a re-emerge the appropriate file is created in /etc/env.d/java and then deleted when previous version is cleaned. I had to unmerge and emerge each in order to have `java-config` work.
What version of portage are you using? emerge -V What versions of the jdk's are you using? emerge -p sun-jdk blackdown-jdk
# emerge -V Portage 2.0.38 [17:44 root@penguin: ~] # emerge -p sun-jdk blackdown-jdk These are the packages that I would merge, in order. Calculating dependencies ...done! [ebuild R ] dev-java/sun-jdk-1.4.0-r6 [ebuild R ] dev-java/blackdown-jdk-1.3.1-r7
Can you try this on portage-2.0.40 please? I'll be looking into it in the meantime.
portage-2.0.40 still does the same :-( ... # emerge sun-jdk <snip> --- !empty dir /opt --- !empty dir /etc/env.d/java --- !empty dir /etc/env.d --- !empty dir /etc --- !targe sym /usr/lib/mozilla/plugins/libjavaplugin_oji.so --- !targe sym /opt/sun-jdk-1.4.0/jre/lib/i386/server/libjsig.so --- !targe sym /opt/sun-jdk-1.4.0/jre/lib/i386/client/libjsig.so >>> original instance of package unmerged safely. * The Mozilla browser plugin has been installed as /usr/lib/mozilla/plugins/libjavaplugin_oji140.so >>> Regenerating /etc/ld.so.cache... >>> dev-java/sun-jdk-1.4.0-r6 merged. >>> Recording dev-java/sun-jdk in "world" favorites file... * GNU info directory index is up-to-date. * IMPORTANT: 2 config files in /etc need updating. * Type emerge --help config to learn how to update config files.
This is/should-be fixed in >=2.0.41 2.0.42 will be public.
carpaski, if this is now fixed, I'll assign it to you to resolve it.
