The kdebindings ebuild still looks for java in /opt/java (see recent gento-user report). It needs to be ixed. You (karltk) said you'd do so but haven't yet, so I'm initially assigning this to you.
Also a bit off the topic, I think that the JDK and JRE should have the same directory structure (jre in /opt/blackdown-ver/jre/* for both), so that the plugins will stay in the same place, or alternatively, have a $JAVAPLUGINDIR or similar that pointed to the root plugin dir. This will make things more uniform and easier for stuff like mozilla that adds the symlink for the java plugin. I know the JDK and JRE packages do it as well, but what if mozilla was merged *after* JAVA .... ?
this will also be needed for dev-lang/swig I think.
The uniformity of a JDK/JRE is a bit tricky, really, since the directory layout is specific to each JDK/JRE. The most-used JDK/JREs are of course those based on the Sun distro, so they are fairly similar. But kissme, japhar, kaffe, sablevm etc are completely different. Also, some packages rely on the fact that the directory layout is different in the JDK and the JRE packages. We debated having /opt/java around, and having the contents of /opt/java be standardized, but we decided against it at the time, since the offical way of specifying the location of java is the env var JAVA_HOME. However, we should perhaps cook together a java-config script that can tell us the interesting paths, ie java-config --plugin-dir or java-config --java-home.
I understand you are perhaps looking for a new, better, global solution. To return to the bug' original topic, if there is somthing already in place, can we quickly change kdbindings to work with that? (e.g to look somewhere else than /opt/java that will work)
Sorry, just saw you modified the kdebindings ebuild. I'm emergng it now and it's working (configure recognized the java in the dir specified). So you can close this bug. (I'm not closing it because of the general java discusion in it).
