Public SourceMage Discussion List

[Jason Flatt <jflatt AT sourcemage.org>]

When there is a version bump for the j2sdk-bin spell (and, I'm assuming, 
though I haven't tested, the j2sdk spell, as well), the PATH gets changed, 
because the version number is in the directory name.  The problem is that the 
new PATH doesn't take affect until a re-login, and if db (I don't know if 
anything else has this same behavior) is dependant on j2sdk, it wants to 
rebuild because of the TRIGGERS file, but can't because "no acceptable Java 
compiler found in $PATH".  Clear as mud?  What I'm wondering is if we should 
add something to the j2sdk-bin spell, like sourcing the profile file in 
FINAL, or is this just one of those things that we will have to deal with?

$ cat /etc/profile.d/java.sh
#!/bin/bash
#
JAVA_HOME=/usr/lib/j2sdk1.4.2_09

export JAVA_HOME
export PATH=$PATH:$JAVA_HOME/bin

-- 
Jason Flatt
Source Mage GNU/Linux: Linux so advanced, it may as well be magic.
http://www.sourcemage.org/
jflatt AT sourcemage.org

Attachment: pgpvc5liZGWV8.pgp
Description: PGP signature