BIND 10 #615: custom configurations, ports,
BIND 10 Development
do-not-reply at isc.org
Tue Mar 8 16:43:21 UTC 2011
#615: custom configurations, ports,
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: UnAssigned
Type: task | Status: reviewing
Priority: major | Milestone: A-Team-
Component: | Sprint-20110309
Unclassified | Resolution:
Keywords: | Sensitive: 0
Estimated Number of Hours: 0.0 | Add Hours to Ticket: 0
Billable?: 1 | Total Hours: 0
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => UnAssigned
* status: accepted => reviewing
Comment:
Hello
I did part of the features needed to complete this, providing a way to
specify a configuration file (both to b10-cfgmgr and to bind10). I'd like
to get it reviewed, while I work on the other features in parallel,
because they are unrelated (at last in the code, even when needed for the
same purpose). I'd like to merge this and keep the ticket open for the
other things (or, some of them already have separate tickets).
I tried to test whatever possible (eg. parsing of arguments). I didn't do
full parsing tests for boss (only of the new options, the old ones didn't
get the tests yet, should I add them as well now?). But there are things I
have no idea how to test ‒ starting whole bind10 seems wrong, to see if
the correct arguments are passed to subprocess. Any ideas how to mock that
up?
I propose this changelog entry:
{{{
[func] vorner
It is possible to specify a different directory where we look for
configuration
files (by -p) and different configuration file to use (-c).
}}}
This code is at trac615, current head is
9dcb53261abe3c16324155fbc4c3436100b9e2ee. For the other tasks I will start
new branches.
--
Ticket URL: <https://bind10.isc.org/ticket/615#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list