"J.P.Lewis" wrote:
> 
> I agree that there should be at least a vague convention on how/where
> Java programs are installed under Unix/Linux.  At present, suppose
> you want to release a rpm'd or similar public version of a program -
> where should it go?

This is what I mean.  If I write a normal linux app, then I know the
default is /usr/local & there are relatively standard places for the
docs, libs, man pages, config files..., but at the moment with java
everyone does things their own way.

> 
> Probably the java community should propose the solution -
> otherwise some poorly chosen convention might take hold.
> I think a couple more people should join the original poster
> and publish a more formal looking recommendation.

I'd be happy to collaborate with other people on this, or if people just
wnat to post comments, criticms to a doc that I put together then revise
according to feedback then that would be fine too.
 
> R.e. the specific proposal, no problems with what's there,
> but I think Java programs may need to exist in places
> other than just /usr/local.  If someone wrote a system control
> panel using swing (e.g. replacement for the redhat scripts
> such as adduser that use tk), where should this go?

Actually I didn't neccesarily mean for the root of the dir-structure I
proposed to neccessarily go in /usr/local.  At the moment on my machine
it sits in a dir called ~/Java though this brings up a very good point
(which I hadn't considered) about how to go about intergrating both
system wide (ie. /usr/local) and user java stuff (in the users home dirs
on multi-user systems).
 
Thanks
Maksim.

> -----------------------------------------------------------------------
> j.p.lewis                                               [EMAIL PROTECTED]
> 012 345 6789                                     //www.idiom.com/~zilla

-- 
Maksim Lin

"...handing C++ to the average programmer seems roughly comparable to
handing a loaded .45 to a chimpanzee."
                                                         -- Ted Ts'o

Reply via email to