On Saturday 04 June 2005 02:23, Kornelis Sietsma wrote:
Changing the "java" and "javac" groups will change all of their slave packages as well, updating all those symlinks with two commands. The "java_sdk_sun" and "jre_sun" groups change one or two symlinks each, from memory, I'm not sure what they are for but included them for completeness. but running "update-alternatives" four times will change *all* the symlinks, and do so in a way that should be compatible with all jpackage.org java packages.
Thanks, I missed from your first response that one of these commands could update a whole group of symlinks. I feel much better now :) And you can do in in one go if you make the assumption that you know what the response should be: #!/bin/sh # Switch to Java 1.5 by changing symlinks in /etc/alternatives echo 2 | update-alternatives --config java echo 2 | update-alternatives --config javac echo 2 | update-alternatives --config java_sdk_sun echo 2 | update-alternatives --config jre_sun I saw Sang Shin give his talk "Roar of the Tiger" yesterday, and after that, I am totally committed to switching all our systems at work to 1.5 (assuming we don't uncover any compatibility issues). So this solves a big hurdle for testing, as all our web servers (as well as a number of standalone machines in the factory and warehouse) run SUSE Pro.
The jpackage.org stuff is pretty nice, imho, though it has the problem that a huge number of other tools assume that Java software is packaged as it comes from Sun or whoever distributes it
I think it's nuts; anything that relies on such a Medusa of symlinks to symlinks to symlinks is an offense against nature :( OTOH, now that I understand the use of update-alternatives, my headache is going away.
for example, I don't use the jpackage/SuSE version of Tomcat, even though it gives nice system integration, as it breaks some tools that assume Tomcat files are all in exactly the right places (specifically, appFuse :) even with the mass of symlinked directories provided.
I had to provide quite an elaborate HOWTO at work to set up Tomcat with Apache using mod_jk, but it works beautifully. But I'm wondering what to do about Tomcat 5.5... does 5.0 run well under Tiger?
But generally, it's a good way to integrate java tools and applications into Linux, and is rapidly becoming a "standard", albeit one that Sun seem uninterested in supporting...
I'm not convinced yet :| Note that /usr/share/doc/packages/jpackage-utils/README.SUSE says you can't install the packages from jpackage.org anyway, at least in 9.2. Haven't checked yet to see if this works in 9.3. -- ====================================================== Glenn Holmer (Linux registered user #16682) ====================================================== "Greater coherence cannot be achieved. Not even the Netherlanders have managed this." -Anton Webern ======================================================