Public SourceMage Discussion List

[Jason Flatt <jflatt AT sourcemage.org>]

On Tuesday 18 October 2005 08:46 am, Jeremy Blosser (emrys) wrote:
> On Oct 18, Jason Flatt [jflatt AT sourcemage.org] 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?
>
> Should we do something like we do with firefox, and create a /usr/lib/j2sdk
> directory to use as JAVA_HOME?  The current /usr/lib/j2sdk<version> would
> then be linked to or from /usr/lib/j2sdk.

That would work, too, and would probably be a better solution.  I'll have to 
experiment with it, which will mean lots of time waiting for compiles.

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

Attachment: pgpianVtDW39q.pgp
Description: PGP signature