Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Jul 2006 19:18:03 -0600 (MDT)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        marcel@xcllnt.net
Cc:        marcel@FreeBSD.org, yar@comp.chem.msu.su, cvs-all@FreeBSD.org, src-committers@FreeBSD.org, ru@FreeBSD.org, cvs-src@FreeBSD.org
Subject:   Re: cvs commit: src/usr.sbin/kldxref Makefile
Message-ID:  <20060731.191803.270754578.imp@bsdimp.com>
In-Reply-To: <8F70D2AC-029E-4829-A775-600D6AABE69E@xcllnt.net>
References:  <EE87FDC1-709D-4B95-9A74-DFF393796664@xcllnt.net> <20060731163209.GB50797@comp.chem.msu.su> <8F70D2AC-029E-4829-A775-600D6AABE69E@xcllnt.net>

index | next in thread | previous in thread | raw e-mail

In message: <8F70D2AC-029E-4829-A775-600D6AABE69E@xcllnt.net>
            Marcel Moolenaar <marcel@xcllnt.net> writes:
: I think the problem is inherent when the existence of the variable
: counts and not its value. It's not intuitive and people use it in
: different ways because of that. I personally like something simple
: like SHARED=NO or SHARED=YES. The lack of definition then meaning
: the default setting. This is trivially implemented with SHARED?=YES.
: Anyway: that's just me...

NO_SHARED=no has been a long-running joke around the office.  However,
going to a simple SHARED=?yes/no won't work either.  It is
inconsistant with the new world order.  I'd expecte that
MK_SHARED=yes/no would be the right thing to do, but there may be
parse time issues that makes it hard to do this simple fix..  

Warner


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060731.191803.270754578.imp>