From: ludo@gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: isc-bind service draft
Date: Thu, 30 Nov 2017 18:03:40 +0100 [thread overview]
Message-ID: <877eu73dhv.fsf@gnu.org> (raw)
In-Reply-To: <87h8tkm629.fsf@gmail.com> (Oleg Pykhalov's message of "Fri, 24 Nov 2017 11:31:10 +0300")
Hi Oleg,
Oleg Pykhalov <go.wigust@gmail.com> skribis:
> Here is a new working in vm version. There is still a lot work to do:
>
> - More apropriate for everyone default config.
> - Writing tests.
>
> More suggestions are welcome :-)
That looks neat! With doc and a couple of examples, and indeed a test,
it would be perfect. But you’re almost there, no?
> (define-record-type* <bind-options-configuration>
> bind-options-configuration make-bind-options-configuration
> bind-options-configuration?
[...]
> (allow-recursion? bind-options-configuration-allow-recursion? ; list
> (default (list "127.0.0.1")))
> (allow-transfer? bind-options-configuration-allow-transfer? ; list
> (default (list "none")))
> (allow-update? bind-options-configuration-allow-update? ; list
> (default (list "none")))
> (version bind-options-configuration-version ; string
> (default "none"))
As a matter of style, I would use question marks only for Booleans.
Here these appear to be enumerations and strings, no?
> (hostname bind-options-configuration-hostname ; string
> (default (gethostname)))
Not a great default (for instance if you’re configuring a remote
machine). Should we just not provide a default?
Thank you!
Ludo’.
next prev parent reply other threads:[~2017-11-30 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 20:11 isc-bind service draft Oleg Pykhalov
2017-11-15 4:48 ` Chris Marusich
2017-11-16 3:21 ` Chris Marusich
2017-11-16 16:18 ` Ludovic Courtès
2017-11-24 8:31 ` Oleg Pykhalov
2017-11-30 17:03 ` Ludovic Courtès [this message]
2017-11-16 16:19 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877eu73dhv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=go.wigust@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.