Subject: Re: HEADS UP: Package removal candidates
To: Thomas Klausner <firstname.lastname@example.org>
From: Jim Wise <email@example.com>
Date: 12/05/2005 18:49:24
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 6 Dec 2005, Thomas Klausner wrote:
>Since Krister has been doing bulk builds for a long while now, I'm
>quite sure that he knows how to configure bulk builds correctly,
>so I'm convinced that something's missing or broken in the packages,
>not the bulk build setup.
With due respect, the setting of `JAVA_HOME' is a basic requirement on
_all_ platforms on which java is used. It is as elementary as setting
PATH for unix command line work, or CFLAGS for C development.
If JAVA_HOME is not set during the bulk build process, the bulk build
process is in error.
If this package is removed because the bulk build process is in error, I
will re-import it.
>I don't presume to know much about how java is supposed to work in
>pkgsrc. However, I don't think that JAVA_HOME is a variable that
>should be set by the user (or system, or bulk build administrator).
Actually, JAVA_HOME is _clearly documented_ in
pkgsrc/mk/defaults as a user-settable variable. I'm not sure where you
got the idea that it wasn't...
A user should not expect random java builds in pkgsrc to work if
JAVA_HOME is unset, any more than he should expect random c builds to
work in pkgsrc if /usr/bin is not in PATH.
It's also worth noting that the very fact that these packages built
successfully in bulk builds for several _years_ before last April shows
that it is the bulk build system which has changed, not the packages
(which have not been updated).
>Thanks for the feedback on ap-jserv.
You're very welcome!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)
-----END PGP SIGNATURE-----