Public SourceMage Discussion List

[David Kowis <dkowis AT shlrm.org>]

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

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?
> 
This also happens with things like casting apache and apr0 or apr. A new
shell has to be created so that apache can find apr. It may not be
apache that's got the problem, but I've had to do this a few times with
different spells.

IMO it should be the spell that modifys /etc/profile that does the
reloading to ensure that any other spells following it have that
information. Not the other way around.

- --
David Kowis

ISO Team Lead - www.sourcemage.org
SourceMage GNU/Linux

Progress isn't made by early risers. It's made by lazy men trying to
find easier ways to do something.
  - Robert Heinlein

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFDVYO+tgErhgxHMHsRAlUtAJ0c+MeeWuNWHre776Au92MqNoc69wCggmew
JDAa+qnHd1zIk0UnGfYkmP8=
=RfqT
-----END PGP SIGNATURE-----