3868 – forte JDK_HOME conflict

Bug 3868 - forte JDK_HOME conflict

Summary: forte JDK_HOME conflict

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Karl Trygve Kalleberg (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-06-18 19:27 UTC by Jacob Perkins
Modified:	2003-02-04 19:42 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jacob Perkins 2002-06-18 19:27:00 UTC

This is in regards to the forte-3.0.ebuild.  It probably shouldn't add a new
JDK_HOME to the environment since it depends on java and gentoo's java setup
will take care of that.  Also, forte installs to /opt, but the JDK_HOME in
21forte in env.d sets JDK_HOME to /usr/local.

Comment 1 Karl Trygve Kalleberg (RETIRED) gentoo-dev

2002-06-18 21:57:31 UTC

Fixed in -r1

Comment 2 Don Seiler (RETIRED) gentoo-dev

2002-06-18 22:52:22 UTC

(ebuild creator here)  It doesn't add a new JDK_HOME.  The JDKs set the
JAVA_HOME variable.  Forte depends (for whatever reason) on a JDK_HOME variable.
 If anything I guess there should be a way to set JDK_HOME equal to the current
JAVA_HOME variable.  I tried to do this initially but it ended up being set to
the string "JAVA_HOME".  But not setting the JDK_HOME at all will cause a
problem, unless my setup was screwed to begin with.

Comment 3 Don Seiler (RETIRED) gentoo-dev

2002-06-18 22:54:19 UTC

1. Open mouth
2. Insert foot

Going over the JDK files I see they do set JDK_HOME.  My apologies.  I agree
with action taken.

Comment 4 Jacob Perkins 2002-06-18 23:04:06 UTC

Since /etc/env.d/21forte is now empty, couldn't it just be removed?