Public SourceMage Discussion List

[Casey Harkins <charkins AT upl.cs.wisc.edu>]

I would agree with either:

  /usr/share/<package>/<jarfile>
  /usr/lib/<package>/<jarfile>

Another possibility since .jar's are usually self contained, would be to
use /usr/lib/jar. This would keep /usr/lib or /usr/share from getting
filled with sub-directories containing single jar files.

I think /var anything is bad, since a .jar isn't really variable data.

-casey


On Fri, 28 Nov 2003, Robert Helgesson wrote:

> On Fri, Nov 28, 2003 at 14:00:28 +1300, Robin Sheat wrote:
> > I have a program that I'm going to be create a spell or two for (version
> > release and a -devel :) This is written in Java, and uses ant to build.
> >
> > Because it is a java program and not aimed specifically for Linux, it
> > simply creates a .jar file and has a script that runs it. Where would be
> > the apropriate place to put this .jar file. I assume the script could go
> > in /usr/bin, but that doesn't seem right for a .jar.
>
> A possibility, if you are compiling to bytecode, is /usr/share/<package>
> since presumably the jar file is architecture independant in that case.
> But /usr/lib/<package>/ is possibly a bit more intuitive and would be
> the same even if you compiled to a native binary.
>
> --
> /     Robert Helgesson     |--    rycee AT home.se     --\
> \-- GPG Key ID: 41E95A5B --|   http://www.rycee.cx/   /
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>