On Fri, 22 Dec 2000, Guillaume Rousse wrote:
> Ok for a shared directory, but why in /usr/share then ? I'm not a FHS
> guru, but if this correspond to the %{_datadir} rpm macro, i guess its
> purpose is to contains data. Java archives files are in fact both the
> executable and the libraries. So they could be in /usr/bin/java or
> /usr/lib/java.
> Is there any official Mandrake opinion on this ?
Well, they would definately not go in .usr/bin. They are not
executables. You can run it as java -jar my.jar, but `java' is the
executable, not the jar file. Debian, as a dist, seems to be really hard
core on the FHS, but that doesn't mean that they have inspected the java
packages. In my experience, /usr/share is more appropriate that /usr/lib
(I did read the FHS spec a while ago, but don't remember much of it). Then
again, /usr/lib is mostly for shared libraries. Maybe .jars are considered
shared libraries (they are actually). I see /usr/lib/xemacs and
/usr/lib/xmms on my system. But there is also /usr/share/xmms,
/usr/share/emacs, and /usr/share/ant. So the contents are what matters,
and I'm not sure how a .jar file would be classified.
I don't know about Mandrake's commitment to Java. It seems very poor at
best. Supposedly they struck a deal with Sun to include the JDK on the
commercial, but only the commerical, CD. Big deal. The JDK with no
software. There's plenty of free Java software out there thanks to apache
and others. How about they start including some of that. I think, though,
that it would require hiring some one who is in tune with Java, as it
takes special care that other programs do not.
--
Sincerely,
David Walluck
<[EMAIL PROTECTED]>
