From owner-cvs-etc  Fri Apr 17 00:21:03 1998
Return-Path: <owner-cvs-etc>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA24946
          for cvs-etc-outgoing; Fri, 17 Apr 1998 00:21:03 -0700 (PDT)
          (envelope-from owner-cvs-etc)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24823;
          Fri, 17 Apr 1998 07:20:36 GMT
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA24358;
	Fri, 17 Apr 1998 17:19:00 +1000
Date: Fri, 17 Apr 1998 17:19:00 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199804170719.RAA24358@godzilla.zeta.org.au>
To: ache@FreeBSD.ORG, asami@FreeBSD.ORG
Subject: Re: cvs commit: src/etc make.conf
Cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-etc@FreeBSD.ORG
Sender: owner-cvs-etc@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>MOTIF_STATIC was never intended for use by ordinary users.  It is only
>used for package-builders.  Do we add every possible variable in
>make.conf (if so, I have a few dozen more from bsd.port.mk) or only
>have the common cases in here?

Nothing except overrides for defaults in sys.mk should be there.

>Maybe it's time for /etc/make.conf.ports?  (No I'm not kidding.)

Ports and build options should always have been separate from
sys.mk, but there is a problem getting them noticed early enough.
/etc/make.conf.ports should logically be included by bsd.port.mk,
but may be needed when sys.mk is parsed.  This is currently handled
by abusing /etc/make.conf to extend sys.mk.

Bruce