[bind10-dev] --data-path argument
JINMEI Tatuya / 神明達哉
jinmei at isc.org
Tue May 15 18:23:58 UTC 2012
At Tue, 15 May 2012 11:55:50 +0200,
Jelte Jansen <jelte at isc.org> wrote:
> I just merged #1889 (--config-file relative path bug fix), but in the
> review, Haikuo mentioned that --data-path can be slightly confusing to
> users; since this is only used for the configuration file right now.
>
> I don't know if we intended it for other uses, and which ones, but if
> we don't, perhaps we should either change its name, or maybe even
> remove it completely.
I don't have a strong opinion, but I observe that it's common for
complicated products with configuration file(s) to provide a specific
way to locate the configuration file(s) (such as the "-c" command line
option). So it probably makes sense to have a dedicated switch just
to specify the configuration file(s), and, for that, it would be
better to name it accordingly, that is, something like --config-path
or --config-file is better than --data-path.
And, assuming we do that, regarding whether we want to keep
--data-path: again I don't have a strong opinion, but if currently
don't use it for other purposes and don't have an immediate concrete
plan to use it for something else, I'd apply YAGNI and just deprecate
it.
BTW, maybe on a related topic, I wonder why we have both --config-file
and --data-path (or if renamed --config-path). Can't we unify them?
---
JINMEI, Tatuya
More information about the bind10-dev
mailing list