Now that local.ini overrides the default.ini, I would expect the
default.ini not to be ignored but to be overridden by whatever is passed
into couchdb with the -c option, so you only need to specify that which
you want to change, even when you use a local.ini on a specified path.
(patch attached to do this, but against couchdb, should probably be
against couchdb.tpl and/or couchdb.tpl.in but my make-fu isn't all that,
coming from Python.)
The only potential problem I see is if the current way .ini files are
handled does not allow you to *un*specify a particular option, in which
case you'd need to have an option to ignore the default.ini.
If my proposal is not acceptable, perhaps I can rewrite it to an
additional command line option, that does work in this way.
--
- eric casteleijn
http://www.canonical.com
--- couchdb 2009-02-27 12:20:37.000000000 +0100
+++ couchdbnew 2009-02-27 13:45:36.000000000 +0100
@@ -168,7 +168,7 @@
interactive_option="+Bd -noinput"
fi
if test -n "$INI_FILES"; then
- ini_files="$INI_FILES"
+ ini_files="$DEFAULT_INI_FILE $INI_FILES"
else
ini_files="$DEFAULT_INI_FILE $LOCAL_INI_FILE"
fi
