Public SourceMage Discussion List

[Eric Sandall <eric AT sandall.us>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 18 Oct 2005, Jason Flatt wrote:
> 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

That won't work as the environment gets 'cleaned up' afterwards. What
I've been doing (e.g. ant) is to have packages that need those
environment variables source the proper /etc/profile.d/ scripts in
BUILD (or wherever they need the variables set).

Another option is to setup a 'generic' /usr/lib/j2sdk symlink and use
that for JAVA_HOME.

- -sandalle

- --
Eric Sandall                     |  Source Mage GNU/Linux Developer
eric AT sandall.us                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDVSslHXt9dKjv3WERAqscAJoD3XHzMVADCHEER0O2sqA1QyR/KwCgpOG0
WmBpZPk6wJ9i5sLAd1wU3qE=
=LsVj
-----END PGP SIGNATURE-----