From owner-freebsd-java Thu Sep 21 14:42:49 2000 Delivered-To: freebsd-java@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id D844137B43C for ; Thu, 21 Sep 2000 14:42:45 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e8LLgCP15305; Thu, 21 Sep 2000 14:42:12 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma015301; Thu, 21 Sep 2000 14:42:10 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA19786; Thu, 21 Sep 2000 14:42:10 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200009212142.OAA19786@bubba.whistle.com> Subject: Re: cvs commit: ports INDEX In-Reply-To: <200009212057.PAA12804@hyde.ssec.wisc.edu> "from Dave Glowacki at Sep 21, 2000 03:57:30 pm" To: Dave Glowacki Date: Thu, 21 Sep 2000 14:42:10 -0700 (PDT) Cc: freebsd-java@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dave Glowacki writes: > > We need to have a standard way of installing this kind of software. > > Better yet, it should work for any of our Java runtimes (JDK, kaffe, ...?) > > > > For example, we could specify that: > > > > - All JAR files go into /usr/local/share/java/jars (replace > > /usr/local with your favorite ${PREFIX} of course). > > The preferred location seems to be ${PREFIX}/share/java/classes. > That's what I'd seen in other ports and what I copied for > databases/mysql-jdbc-mm > > I think that's still appropriate, since the JVM finds out about > it via your CLASSPATH variable. OK, so ${PREFIX}/share/java/classes seems to be the consensus. And I guess Nate's right that shared libraries belong in ${PREFIX}/lib with the rest of 'em. This also avoids having to do any LD_LIBRARY_PATH hacks. Note that each such port would require an mtree file containing ${PREFIX}share/java/classes. Should there be a special default mtree file for java stuff? > > - Ports should install man pages as well > > I assume this was "ports of Java applications". I think the > standard for Java class documentation (as opposed to Java application > documentation) is HTML generated by javadoc, which IMHO beats the pants > off man pages. I suppose it'd be possible to generate manpages via > the latest javadoc, or via one of the free javadoc reimplementations. What I meant was that if your port adds a script (like my example for sablecc) then it should also add a simple corresponding man page. The man page can be simple and consist largely of a pointer to the 'real' JavaDoc (or whatever) documentation installed in ${PREFIX}/share/doc/foobar. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message