Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 06 Aug 2005 19:08:17 -0600 (MDT)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        phk@haven.freebsd.dk
Cc:        cvs-src@FreeBSD.org, src-committers@FreeBSD.org, ru@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/usr.bin Makefile 
Message-ID:  <20050806.190817.128046221.imp@bsdimp.com>
In-Reply-To: <25357.1123323114@phk.freebsd.dk>
References:  <20050806093614.GI48504@ip.net.ua> <25357.1123323114@phk.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <25357.1123323114@phk.freebsd.dk>
            "Poul-Henning Kamp" <phk@haven.freebsd.dk> writes:
: In message <20050806093614.GI48504@ip.net.ua>, Ruslan Ermilov writes:
: >
: >On Sat, Aug 06, 2005 at 06:56:39AM +0000, Poul-Henning Kamp wrote:
: >> phk         2005-08-06 06:56:39 UTC
: >> 
: >>   FreeBSD src repository
: >> 
: >>   Modified files:
: >>     usr.bin              Makefile 
: >>   Log:
: >>   Put hesinfo(1) under buildoption "YES_HESIOD"
: >>   
: >>   Revision  Changes    Path
: >>   1.283     +5 -1      src/usr.bin/Makefile
: >> 
: >Traditionally, this would be spelled "WITH_HESIOD".
: 
: Yes, but I wanted to clear category for toplevel-only
: build options.
: 
: The WITH_FOO have traditionally been used to control
: single programs, but you can't enable HESIOD in
: amd if it is not also in libc, so the YES_FOO options
: are intended to be usable only for buildworld and installworld
: targets.

I think we need to move to the NetBSD-like way of having
WITH_FOO/WITHOUT_FOO controlling MK_FOO getting set to yes/no (or did
I get that backwards).  Sorting that out, however, might be a pita...

Warner




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