GitLab

Use "make maintainer-clean" instead of "make distclean" to remove the manpages.
This fixes problem where enduser using tarball does a "make clean"
and loses the maintainer-tarball-provided manpages.

This is usually $prefix/var/bind10-devel/. We set mode to 2770 oct.

Include the default sqlite3 database as well. This is easier than
documenting everything and it would just work.

The warning would be provoked by checking a MasterFiles type data
source. The client list skips it, because cache is disabled, and it
complains it won't be able to serve. That is not a problem while
checking configuration, so the zones are stolen from it.

The exception about invalid RR class is not very helpful, so provide a
better one.

They are skipped in the ClientList, so not checked at all.

A small bugfix in the validation is included. There's no test for it
directly - it is tested implicitly in the plugin test, but I wasn't able
to reproduce it on small test spec files. If we weren't planning for
replacement of the whole thing, it would need some investigation.

as opposed to searching the import path; this gives us more flexibility over cfgmgr plugin names, and makes sure they don't conflict with actual modules.

A file was not cleaned.

It caused some naming collisions and the system tests failed because of
this. This is a workaround, the real solution needs to be done anyway.

So users don't have to set it up, but they can disable it if they want.

The cache-enable and cache-zones options are now in the datasrc spec
file.

The file was written previously and not committed to git. Fixing.

also some minor formatting

This was noticed when I tried to commit some merged code.
My git hook noticed the whitespace issues.

catch up for docbook file's changes

reviewed by jelte

Depending on whether config_file is specified, use either the builtin default or os.getcwd() for the data path (so that you can use relative config file names. If an absolute config file is given, data path is ignored).

Also added an info log message specifying which file cfgmgr ends up using.

This reverts commit 6a9dbeff.

Most builder systems use Python 3.1.

This verbosity feature was added in Python 3.2.

- if self.clear_config is None was wrong, should just be if self.clear_config
- 'back up' should have been 'create backup of'
- default value for unused parameter rename_config_file in b10-cfgmgr_test.py.in MyConfigManager should have been False, not None
- reordered message file

also extend log message a bit

Later steps will make sure these are generated for "make dist"
to be included in tarball.

By default, the logging layer should now flush after each message.

Use python_PYTHON for the python scripts. This results in
installing byte compiled version.

Removed files from EXTRA_DIST as they are now in dist by default.

Added CLEANFILES to clean up .pyc in build directory.

Note that I am keeping the installation directory the same.

test's Makefile.am (usual MacOS nit); made sure PY_SSIZE_T_CLEAN is
defined when 'y#' is used with PyArg_ParseTuple.  For the latter, see
http://docs.python.org/py3k/c-api/arg.html#strings-and-buffers

for python logging message scripts.

When they are regenerated by make (not during initial configure run),
they were not set executable, which was useless. This way they are set
executable twice during the initial configure-make-make check, but at
last it works.

Instead of EXTRA_DIST, this allows make to regenerate them on .in
change.