[bind10-dev] configure select components for building/installing

[Shane Kerr]

Jeremy,

On Thursday, 2012-09-13 08:39:18 -0500, 
"Jeremy C. Reed" <jreed at isc.org> wrote:
>   	``You can specify which features to provide in the BIND 
> 10 installation by enabling and disabling components. BIND 10
> includes various components by default. Additional components are
> enabled using the --enable-component configure options, with
> "component" is the name of the feature. Similarly, some components
> may be disabled with the --disable-component options. The option
> --enable-all may be used to select all BIND 10 components for
> installation. Also the --enable-components option may be used to list
> (separated by spaces) each feature. Note that these configure
> switches do not enable/disable components for run-time, but are for
> selecting what software is (or is not) generated and installed.
> 
> 	``For example, the DHCP components can be selected to be
> built and installed with "./configure --enable-dhcp".''

Should we recommend building everything usually, with the idea being
that it doesn't cause any harm if not run?

> We also discussed about how to split it up. (I couldn't find our 
> previous ideas.) Here are my suggestions:
> 
> --enable-resolver
> --enable-auth		# maybe this should be dnsauth?
> 			# also implies zonemgr, xfrin, xfrout, ddns

If we're going to break out the libraries, maybe it makes sense to
break out each component here. It does seem like a good idea to also
have a single option which enables everything you need for typical
authoritative service though!

> --enable-dhcpv4
> --enable-dhcpv6
> --enable-stats-httpd
> --enable-libdns++
> --enable=libdhcp++
> 
> Always built and installed are logging library, bind10 (boss),
> cfgmgr, cmdctl, stats (even though is not ran by default),
> sockcreator, and msgq.  But should consider that these could be
> removed too. In particular, one may want libdns++ (and its
> dependencies libb10-cryptolink and libb10-util and libb10-exceptions)
> and nothing else.

Agreed, but one step at a time...

> (Reminds me we should remove the "b10" from library names that aren't 
> specific to BIND 10 that we want wide use.)

Right now I guess these are libdns++ and libdhcp++. Do we want to
include some of our other utility libraries? (In which case we
probably want to tag them as "isc" in the front or something like that.)
 
--
Shane