Date: Mon, 8 Apr 2002 12:09:20 +0200 (CEST) From: Herve Quiroz <hquiroz@esil.univ-mrs.fr> To: Ernst de Haan <znerd@FreeBSD.ORG> Cc: java@FreeBSD.ORG Subject: Re: Default directory locations for Java ports Message-ID: <20020408113109.D38939-100000@puget.esil.univ-mrs.fr> In-Reply-To: <200204062141.XAA06645@smtp.hccnet.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
> 1) One or more JAR files. Typically one. If there's more than one, then you
> should ask yourself if the port should be split up.
> 2) Javadoc-generated API documentation.
> 3) Other documentation.
> 4) Examples.
> 5) Source files.
What about the naming of the jar file. I have found that every port
installs the jar without its version number but maybe there are some
issues about it. I explain : for jakarta-log4j, there is a 1.1 version
using the Category as the main class, and a 1.2beta with Category changed
to Logger. So maybe we should enforce the ports to install the jar with
the version number : ${JAVA_LIBDESTDIR}/${PORTNAME}-{PORTVERSION}.jar
Maybe a wrapper (a link for a jar file without version number as for
*standard* C libraries) would also fit nicely (again I am maybe just
splitting hairs here ;)).
> Only the JAR file is really mandatory. The other things are optional.
Ok, so what about new /etc/make.conf for specifying user's wishes of
installing src and examples ?
> I propose that the following settings will be used by ports:
>
> 1) JAVA_LIBDESTDIR -- Destination directory for the JAR file(s).
> 2) JAVA_APIDOCDESTDIR -- Destination directory for Javadoc-generated
> API documentation.
> 3) DOCSDIR -- Destination directory for other API documentation.
> 4) EXAMPLESDIR -- Destination directory for examples.
> 5) JAVA_SRCDESTDIR -- Destination directory for .java source files.
>
> Note that this proposal does not specify anything different for the '4) Other
> documentation' and '5) Examples' than other (non-Java library) ports would
> use. This is intentional. I think we should use what is already available, if
> it is really appropriate.
The same way (keeping it close to other ports scheme), I would preferably
make use of JAVA_LIBDIR (or JAVA_LIBSDIR) instead of JAVA_LIBDESTDIR
(respectively for JAVA_APIDOCSDIR, JAVA_SRCDIR). Indeed those variables
could be used by the final user to set his own classpath and then the
"DEST" would not mean anything to him. Splitting hairs once again ;)
> Apart from this first proposal, the second is that we use the following
> values for these settings:
>
> # This setting is only used internally by bsd.java.mk, not by the port
> __JAVA_SHAREDIR= ${PREFIX}/share/java
>
> JAVA_LIBDESTDIR=${__JAVA_SHAREDIR}/lib/${PORTNAME}
> JAVA_APIDOCDESTDIR=${__JAVA_SHAREDIR}/apidocs/${PORTNAME}
> JAVA_SRCDESTDIR=${__JAVA_SHAREDIR}/src/${PORTNAME}
about APIDOCSDIR, what about that :
DOCSDIR=${__JAVA_SHAREDIR}/doc/${PORTNAME}
JAVA_APIDOCDESTDIR=${DOCSDIR}/api
BTW, I see things are moving fast both with java library ports as well as
with native jdk porting. Keep on the good work !
Regards
Herve
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020408113109.D38939-100000>