This is the mail archive of the
java-discuss@sources.redhat.com
mailing list for the Java project.
Re: classpath question
- To: Per Bothner <per at bothner dot com>
- Subject: Re: classpath question
- From: Tom Tromey <tromey at cygnus dot com>
- Date: 13 Sep 2000 19:31:53 -0600
- Cc: "green at cygnus dot com" <green at cygnus dot com>, "'java-discuss at sources dot redhat dot com'" <java-discuss at sources dot redhat dot com>
- References: <01C01B58.9C2953C0.green@cygnus.com> <m266o03u7s.fsf@bothner.com>
- Reply-To: tromey at cygnus dot com
>>>>> "Per" == Per Bothner <per@bothner.com> writes:
Per> There is a proposed Debian policy for Java, and there have been
Per> some suggestions/comments on the debian Java list. Gcj should be
Per> compatible with Debian policy or vice versa, given Debian status
Per> as the GNU OS. I don't believe your proposal is compatible with
Per> the proposed policy.
I re-read this.
First, the policy is just a proposal.
Second, it seems significantly less useful than what Anthony
suggested. In his scheme there is no need to change CLASSPATH if you
are using packages installed systemwide. This is akin to how C
programming works -- install headers and a library, and everybody on
the system is good to go.
I think we should do what makes sense for gcj. We can always provide
a configure flag so that Debian packagers can make gcj works their
way.
Last, I'd rather see Debian change their spec so that the default
CLASSPATH for a compiler would include the packages installed in
/usr/share/java/. They could do this for non-free compilers by
writing a wrapper program (or hacking the existing one in the case of
Sun's JDK).
Tom