On Sun, 8 Jul 2001, David Walluck wrote:
> On Sun, 8 Jul 2001, Edward Avis wrote:
>
> > If not, I propose that Java libraries be installed under
> > /usr/share/java/, either as .jar files or as subdirectories full of
> > .class files. And /etc/profile.d/java should do something like:
> >
> > for i in /usr/share/java/*; do
> > export CLASSPATH=$CLASSPATH:$i
> > done
>
> This is how we do it (we being me and someone else, the only two on this
> list that seemed really interested in Java). Mandrake, as a company,
> doesn't seem to care much. They do not offer the JDK (or are maybe
> prohibited by law). Still, if Sun won't let you I'm sure IBM would love
> too seeing as they say they are pro-Linux these days. I had heard they
> were going to distribute Sun JDK only on the commercial CD, but they still
> do not seem to have an official stance on Java support. There are no java
> rpms in Cooker. for example.
>
> Problem is, in X the ~/.bash_profile doesn't seem to be read, and
> /etc/profile is over-written by msec all the time, so I can't figure out a
> good way to get these into the path except a single script in
> /etc/profile.d would probably do the trick. And you'd probably want for i
> in *.jar instead of * incase there are some directories or properties
> files or something else in that directory,
>
Precedence set by Kaffe pkg, which is atleast in theory compliant with the
standard. /usr/java should be broke apart into /usr/lib, /usr/bin, and
/usr/share/"name". "Global libs" (for lack of knowledge?) would get
installed into the generic CLASSPATH
(/usr/share/"kaffe\jre\jdk\java"/lib), where as application specific would
create thier own dir under /usr/share/"prog\pkg" and use a wrapper to
alter the CLASSPATH. This doesn't mean a socalled global HAS tobe put into
the global path, they could all be stuffed into /usr/share/"prog\pkg" to
allow for version mixing..
About rpm. There is nothing in rpm that would disallow useing two or more
concurrent versions of a package. The problem here is the .rpm's just
aren't designed for this, which is obvious when you rpm -i and get file
conflicts. The way around this is useing a Nomad(tm?) approach. Useing
update-alternatives(?) to reset links as needed on an app by app basis.
--
--Axalon
