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

[JINMEI Tatuya / 神明達哉]

Sending as asked in today's call..

One major feedback I received last week when I gave a short
presentation about BIND 10 was barrier in build/installation, mainly
due to dependency packages.  This is a well known issue, but I think
it's becoming more and more serious as we approach formal releases.
I noticed it because it was a f2f place, but normally we wouldn't hear
such feedback; average candidate users are not so desperate in
installing BIND 10 and just stop trying and forget it.

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
- include boost tar ball in bind10 tar ball
- 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.
- introduce null-encryption mode and/or allowing other crypt lib such
  as openssl (to exclude botan)
- use python2 instead of python3

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

---
JINMEI, Tatuya