Date: Fri, 17 Apr 1998 06:06:27 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> To: Satoshi Asami <asami@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, cvs-etc@FreeBSD.org Subject: Re: cvs commit: src/etc make.conf Message-ID: <19980417060627.25427@nagual.pp.ru> In-Reply-To: <199804170027.RAA10861@silvia.HIP.Berkeley.EDU>; from asami@FreeBSD.org on Thu, Apr 16, 1998 at 05:27:52PM -0700 References: <19980417031022.02794@nagual.pp.ru> <199804170027.RAA10861@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 16, 1998 at 05:27:52PM -0700, Satoshi Asami wrote: > I'm not sure if I agree with that, but that's another point. However, > do developers really need MOTIF_STATIC? That makes EVERYTHING link There is another point of MOTIF_STATIC adding exist too. Since it control MOTIFLIB too (as HAVE_MOTIF), not mentioning it gives reduced picture of things which can leads to confusion related to MOTIFLIB (one example of such confusion you already give). > Seriously though, I don't envision that as a description and default > values for all possible variables. Those should go in bsd.port.mk, bsd.port.mk is default for all systems and not tunable. /etc/make.conf (or similar thing) reflects per-system defaults. I.e. better leave bsd.port.mk untouched and set every non-standard variable values elsewhere. > That means make.conf.ports is empty by default where people can > add things as they wish. But they can do that to make.conf already, > so I guess it makes the whole thing rather pointless. :< Adding things from non-existance is harder than uncomment/edit some pre-existen line, so it will be more comfortable to have _all_ bsd.port.mk variables mentioned in make.conf.ports -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980417060627.25427>