On Fri, 21 May 1999, Hubert Feyrer wrote:

: > - The following extra settings will be added to CONFIGURE_ENV:
: >     PERL_PATH="${LOCALBASE}/bin/perl"
: >     PATH_PERL="${LOCALBASE}/bin/perl"
: 
: 1. Why be redundant here and
: 2. Where is this (supposed to be) used?

I ahouls have qualified that to be "...for GNU_CONFIGURE".  Many packages
that use GNU_CONFIGURE and check for Perl's path allow one of these two to
override the path.  This ensures that the "correct" perl is used, even if
another copy is earlier in $PATH.

: > - The value MAKECONF=/dev/null will be added to MAKE_ENV in order to prevent
: >   packages which use BSD Makefiles from using unintended defaults from
: >   /etc/mk.conf.  (This may be accompanied by other NOxxxxx=1 variables which
: >   uniformly lay out the functionality of BSD Makefile based packages.)
: 
: I don't know why, but I'm feeling uneasy about this.

I feel pretty uneasy about the fact that the BSD makefiles used in some pkgs
(mit-pthreads, for example) _are_ affected by mk.conf changes.  That causes
way too many PLIST inconsistency issues.  The necessary stuff (CC, CXX,
CFLAGS, ...) are passed in the environment by bsd.pkg.mk; all else should be
"system default" and not altered _again_ by mk.conf.

-- 
-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)