Hello.
1) Too work intense approach to integrate Sun Java?
Someone reported at freenode's ##java that make-jpkg does not work with
Java 1.6.
I wonder why that is?
Isn't it so that regardless of what is contained in a Sun JDK/JRE
archive that you need to extract all of it, maintaining the folder
structure, and then have the few key binaries hooked up via symlinks and
some trickery to ensure that "class path" is correct (either by relying
on Sun's binaries figuring it out properly or by setting the CLASSPATH
environment variable)?
If that is all so, wouldn't make-jpkg be able to work with all Sun
JDK/JRE archives (past and future), provided they maintain the
up-to-this-point-known binary names properly, so that creating the
symlinks works the way it should?
2) Faking Java on modern Linux distros:
This may seem like the place for a complaint too:
Can everyone please stop placing executables called "java" and "javac"
which are not Java on Linux distributions? Java has enough issues,
adding to them like this is not helping, rather the opposite. (It
doesn't help conveying a professional image of the Linux distribution
either.)
(Has anyone ever considered asking the vendors of all these
not-really-Java projects wether they agree with using their projects to
fake Java compatibility in this outrageous form? I surely would disagree
with my incompatible software being used to fake an impression of
compatibility which is just so unrealistic as in the case of gcj and co.)
With best regards
Blackwell
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
