-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
What is the convention for RPMs of compiled Java libraries?
Some packages put the code into a .jar file and install this under
/usr/share/java. Then I think it is up to the user to make sure that
the file is included in CLASSPATH, eg:
% export CLASSPATH=$CLASSPATH:/usr/share/java/whatever.jar
I have my .bashrc set up to do this automatically for every file in a
certain directory. It would be possible to add a new script in
/etc/profile.d/ to do this.
Sun sometimes recommend that you install new .jar files in
/usr/java/jre/lib/ or /usr/java/jre/lib/ext/. Then they get picked up
automatically without needing to be in the CLASSPATH. But I think this
is not really appropriate for stuff that doesn't come from Sun, and I'm
not sure that /usr/java/ is a good place for anything, although Sun seem
to have claimed it.
One guy has packaged lots of Java stuff for Red Hat's contrib section,
for example
<http://www.rpmfind.net/linux/RPM/solaris//RPMS/i386//Acme-1.0-2.noarch.html>.
This installs a tree of .class files under /usr/share/Acme/ and adds two
new scripts to /etc/profile.d/ to add this directory to the CLASSPATH.
Personally, I think that having every package add a new script to
profile.d/ is messy. Better to have a single one and have it
automatically pick up things installed under some specified directory.
So is there a Mandrake policy or precedent for this stuff? Do any other
distributions have a policy we could copy?
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
Comments?
- --
Ed Avis <[EMAIL PROTECTED]>
Finger for PGP key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7SGS0IMp73jhGogoRAlr5AJ0RRmAiQxjYt40DHsWCF201GNTL4QCfRJwP
yuHUuIGPFb0E02/gooQj2nw=
=N42k
-----END PGP SIGNATURE-----
