Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] j2sdk Question . . .

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: "Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] j2sdk Question . . .
  • Date: Tue, 18 Oct 2005 10:46:40 -0500

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.

> $ 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

Attachment: pgpGCsNtjwPmI.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page