-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 8 Jul 2001, David Walluck wrote:
>>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
Hmm... in that case there is no 'Mandrake policy' on Java. Unless
things like Kaffe and GNU Classpath are packaged and actually used. I
ask because I want to create RPMs of some (free) Java libraries and I
want to know where to put the files. If there isn't a Mandrake
convention for this stuff then we could look at what Red Hat do.
Some RedHat contrib packages install in /usr/share/java/ (good) and
install a new script in /etc/profile.d/ for each package (bad). But
that is only contribs, I wonder what happens for the main part of the
distribution? Do Red Hat even put any Java libraries into the main
distribution? I'll have to go and check.
(And if SuSE, Caldera, TurboLinux or any of the other semi-proprietary
RPM-based distros have some convention for Java, we could look at that.
Also see what Debian, Slackware and Stampede do. I'm sure Debian has
some well-thought-out Policy on Java stuff.)
>There are no java rpms in Cooker. for example.
So I wouldn't contribute the packages I build into Cooker-contrib,
because they'd be a bit useless without a JDK to run them on. But I
would still like to get them 'out there' for RedHat-like systems.
>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.
Yes, that's what I'm suggesting. Install a file in /etc/profile.d/.
This is the Right Way to set environment variables because it's just a
file you can install or uninstall with RPM - no patching or appending to
existing files.
>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,
I thought the directory might contain subdirectories of .class files
too. Some Java libraries are still distributed this way rather than as
.jar files.
If you think that /usr/share/java/ might be used for stuff other than
compiled Java classes, then create a subdirectory
/usr/share/java/classes/ and add the contents of that to CLASSPATH.
Although this conflicts with what some other people are doing, putting
stuff directly into /usr/share/java/.
Maybe say that we should add:
- - /usr/share/java/*.jar
- - /usr/share/java/classes/*
to the CLASSPATH.
- --
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
iD8DBQE7SWTrIMp73jhGogoRAlwSAJ0URlqNEQcQprdzyuXZfzPUHlydBQCfcmBK
qppNX+39F39Xz/k5/4X0SH4=
=9dbp
-----END PGP SIGNATURE-----
