GitLab

report-cpp-coverage wasn't working because of a syntax error
Added coverage target to .NOTPARALLEL to run unit tests and only then build reports.
Fixed cppcheck.

Remove the clean-python-coverage and report-python-coverage make
targets.  Remove the configure report output at end about Python
code coverage.  The pycoverage support was removed six months ago.

 - Logging section updated.
 - Missing coma in kea.conf.pre added
 - ${localstatedir}/log is now created

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

exclude include/ so will remove /usr/local/include too

also add a hack to change the paths to be consistent
in the case that the directory the job is done in is a symlink
to another directory.
(Alternative method would be to run the lcov tool multiple times
for each path and set the base-directory switch plus add-tracefile
switch to combine.)

I didn't get this reviewed. I am under assuption that this make target
is rarely used.

Rather than using terminal-specific hard-coded escape sequences that are
not guaranteed to work on all terminals, use the tput utility. Also use
the terminal defined standout mode rather than trying to set a specific
colour. The old way enabled bright yellow text which, while very visible
if your background is black, is all but invisible if your terminal
background is white.

The joker in the pack here is io_address.h, required by the DHCP
header files.  That refers to the headers-only version of Boost
ASIO included in the BIND 10 source kit, so the ASIO files need
to be copied as well.

These files are to allow the authors of hooks callouts to compile
their code.  At the moment only the DHCP files are installed; the
DNS files will be added once hooks have been added to the DNS servers.

It seems to check more and run longer. It also produces bunch of new
warnings.

This reverts commit 6ce96d1b.

This should have gone to a branch, not master :-|.

It seems to check more and run longer. It also produces bunch of new
warnings.

The directory has been wrong for a long time.
Reviewed via jabber.

... in case someone wants to autoreconf from a tarball.