GitLab

Conflicts:
	src/lib/dhcpsrv/tests/daemon_unittest.cc

This change affects many files using the Configuration object and types
derived from it.

Comments have been improved in one file.  The other contains a test
that alters logging, so a test fixture has been added that ressets
the logging back to the default in its destructor.

Recently the "pool" parameter has been renamed to "pools" and its type
was changed from the string to a map. The kea.conf was not updated to
use the new format for the pool definition. This change corrects it.

Some unit tests in dhcpsrv altered the logging configuration but
never reset it. That configuration was then used for subsequent
tests and made them overly verbose.

Previously, the logger configuration was applied (to log4cplus) as soon as
it was parsed. We decided in the jabber discussion that the logger
configuration should only be applied if the whole configuration goes
through. So, the logger configuration is now 2-stage: parsing and commit
as for other configuration parameters.

Some tar implementations cannot or do not auto detect the compress format.
For example, I saw today:

$ tar xvf kea-0.9.tar.gz
tar: Cannot identify format. Searching...
tar: Cpio file name length 41449 is out of range
tar: Invalid header, starting valid header search.
...
tar: Cpio file name length 39676 is out of range
tar: End of archive volume 1 reached
tar: bcpio vol 1, 0 files, 3811899 bytes read, 0 bytes written in 1 secs (3811899 bytes/sec)
tar: Unexpected EOF on archive file

Did say 0.9-beta1 for 0.9 release for example.
So added the __VERSION__ macro.

Note that this may look ugly in the "git" branch or other
odd named versions but will match names if a dist tarball
was created from git master. But will be correct for official releases.

Okayed via jabber.

This was probably never seen anyways so I didn't adjust for Kea.
Okayed via jabber.

On line 21 use two tabs before the committer username.
On line 21 use a tab before the keyword type.