[bind10-dev] splitting up BIND 10 to install different features

[Michal 'vorner' Vaner]

Hello

(Resending to the list, I forgot to press G once again…)

On Wed, Feb 15, 2012 at 10:23:06AM -0600, Jeremy C. Reed wrote:
> - configure switches to select what components are built and installed

I think this would be the way to go. It seems easy enough to enable/disable
parts by ifdefing parts of makefiles and there'd be only little change for the
developers. It is better to develop it as a whole, because then we'd have to
take explicit care about which version of which repository we have, and we often
do changes across the boundaries, no matter how we split them, which would be
problematic in case of separate repositories.

Different install targets is bigger task to set up in the build system and could
be more surprising for a user (I kind of expect to influence what is built and
installed by configure, but having to call different install targets is
something I never saw). Also, building something I'm not going to install is a
waste (and not a small one, the C++ code is really expensive to build, maybe the
most expensive of the often used languages).


I'd group them something more together, this looks like split too much and users
well hate us if they need to install 13 different packages to start an
authoritative server only. I'd group it by functionality, eg. something like
this way. Also, some of them is just few hundred lines of python code, so
there'd possibly be more of the package handling code than the real code.

bind10-core {
> bind10-core: msgq, cfgmgr, boss, sockcreator, related python modules, 
> libexceptions, and libcc.
> 
> bind10-control: bindctl, cmdctl, related python libraries
> 
> bind10-libs: libcfgclient, liblog, libstatistics, and other libraries
}

bind10-dns-core{
> bind10-dnslibs: libdns++, libdatasrc, libacl, etc.
}

bind10-auth {
> bind10-auth: b10-auth, b10-xfrin, b10-xfrout
}

bind10-resolver {
> bind10-resolver: b10-resolver
}

bind10-stats {
> bind10-stats: b10-stats
> 
> bind10-stats-httpd: b10-stats-httpd
}

bind10-dhcp {
> bind10-dhcplibs: libdhcp++
> 
> bind10-dhcp6: b10-dhcpv6
}

> By the way, we really should rename many of these libraries to include 
> isc or bind10 or b10 as part of their names. I think there is a ticket 
> for this but didn't find yet.

Or, have them in a subdirectory? Like lib/isc/bind10/libcc.so?

With regards

-- 
  I'm a dragon, and I will not be ignored, not even by a tree!
       Saphira Brightscales

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20120216/78fdd6dc/attachment.bin>