[bind10-dev] address dependency problems for beta/release

Francis Dupont fdupont at isc.org
Tue Nov 27 18:53:08 UTC 2012


> This is a list of random ideas of improving the situation.  Some may
> be too hard, and some may not make much sense, but I'm listing the for
> food of thought:
> 
> - (try to) push ports/pkg/etc to various OSes/distributions before beta

=> before it should be useful to:
 - improve the system (specific) notes (both in content and in scope,
  BTW for the second do you know on which systems they tried?)
 - make people to know what/where/etc system notes (perhaps rename them
  HOWTO and include them in a very visible way in distribs?)

> - include boost tar ball in bind10 tar ball

=> to build boost is far harder than to build bind10 so I can't see
how it could be interesting.

> - introduce libdns++-only build mode (for those who don't need to run
>   BIND 10 servers, and there is indeed such a user).  this mode
>   wouldn't require log4cplus or sqlite3, and maybe not even Python.

=> there are some blocking dependencies in libdns++ which I agree
should be allowed to be disable one by one. BTW I like the Python
bindings.

> - introduce null-encryption mode and/or allowing other crypt lib such
>   as openssl (to exclude botan)

=> the crypto is a good example of something which is not needed
in 95% of the libdns++ (in fact only tsig uses it).

> - use python2 instead of python3

=> the C and many details are different: IMHO it makes sense to add
python3 support in a python2 code (forward way), not in the opposite
(backward) way.

> My suggestion is to include at least some of these in our goals of
> beta/release.

Regards

Francis Dupont <fdupont at isc.org>


More information about the bind10-dev mailing list