BIND build knobs

[Doug Barton]

On Fri, 24 Sep 2004, Bjoern A. Zeeb wrote:

> On Fri, 24 Sep 2004, Doug Barton wrote:
>
>> Kris Kennaway wrote:
>>> On Fri, Sep 24, 2004 at 01:42:00PM +0000, Ruslan Ermilov wrote:
>>>
>>>
>>>>  Log:
>>>>  Don't expose BIND libraries and their headers to the public by default,
>>>>  but have a knob (WANT_BIND_LIBS) to build and install them in /usr/lib
>>>>  and /usr/include.  Rumors are that this may be useful at a later point,
>>>>  let's see.
>>>
>>>
>>> The naming of this is inconsistent with the ports collection: WANT_*
>>> variables are for internal port use only, and may not be set by the
>>> user.  User control switches are in the WITH_*/WITHOUT_* namespace.
>>
>> Argh, thanks. I had this thought in the back of my mind, but got it
>> backwards. We'll get this fixed.
>
> well actually for the base system shouldn't things be named NO_* ?

Only if what you want is to disable things. As was already pointed out, 
the knobs are boolean, it's either defined or it isn't, regardless of 
what the knob is named.

The goal here is to make the NO_BIND option a lot more granular, and to 
default some of the options to not install bits unless they are 
specifically requested. The knob for the libs is the first step in the 
latter direction.

The other knobs I have in mind are as follows:

#NO_BIND_DNSSEC=        true    # dnssec-{keygen|signzone}
#NO_BIND_LWRESD=        true    # lwresd
#NO_BIND_NAMED=         true    # named, named-check{conf|zone}, rndc[-confgen]
#NO_BIND_UTILS=         true    # dig, host, nslookup, nsupdate

At the bay area bsdcon developer's conference, it was agreed that we 
would introduce these knobs for 5-RELEASE, and in HEAD we would turn 
some of them off by default. The likely candidates for swithing from 
install by default to install on demand are named and the dnssec stuff.

I'm open to other names for the install on demand knobs. I thought that 
emulating the ports syntax would make the intentions more clear to the 
users, but I'm ok with whatever folks think will work well.

Doug

-- 

     This .signature sanitized for your protection