the blackdown-jdk installs to /opt/blackdown, shouldn't it have a link to /opt/java? it appears to cause problems with the php install
I discussed this with chouser last year and we decided that the /opt/java symlink is a bad idea for the following reasons: 1) The contents of the /opt/java directory is different, depending on the actual JDK or JRE you install. 2) There is a big difference in layout even between a JRE and JDK from the same vendor 3) When one installs a Free JVM, such as kissme, japhar or kaffe (we don't have finished ebuilds for this yet), the /opt/java would link to /usr which seems a bit silly. My proposed remedy is as follows: 1) All JDK and JREs set CLASSPATH and JAVA_HOME in /etc/env.d/20java 2) All JDK and JREs provide /usr/bin/java-config that can be used to query - VM version - location of java, javac, jar or any other executable of interest, and necessary parameters - preferred CLASSPATH and JAVA_HOME - other necessary environmental settings - knowledge about optional java libraries (jaxp, java-gnome, etc...) This is preferrable since it would be trivially possible to default to Jikes as the compiler without having to put shitloads of logic into the ebuilds, as we do now. java-config can compose a complete and working CLASSPATH for a set of jarballs, and even take care of proper versioning. The alternative to this would be to enforce a common layout in /opt/java that all ebuilds can rely on, but this proved troublesome as some applications' configuration scripts got confused when I tried to "clean" the directory structure in /opt/java too much.
Thanks for the explination. I'll agree that this sounds like a much better approach.
