Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Fri, 27 Feb 2009 18:27:47 +0000
From: Noah Slater <nslater@apache.org>
To: dev@couchdb.apache.org
Subject: Re: Proposal: let -c *not* ignore default.ini
Message-ID: <20090227182747.GA5773@tumbolia.org>
Mail-Followup-To: dev@couchdb.apache.org
References: <49A7E7F2.2080204@canonical.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49A7E7F2.2080204@canonical.com>
User-Agent: Mutt/1.5.18 (2008-05-17)

On Fri, Feb 27, 2009 at 02:17:38PM +0100, eric casteleijn wrote:
> 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.

We cannot accept this patch as is, because it provides no way to avoid the
default configuration file. As it currently stands, if you wish to use some
custom configuration file, it assumed that you know enough about what you're
doing to add in the default or local configuration files as well.

To accept your patch, we would need an additional option, like you mention:

  --ignore-default-configuration

For me, this weird behaviour breaks the rule of least surprise.

Even with the modification suggested, I doubt I would want to accept this patch.

I suggest that you use the following on your local system:

  couchdb -c default.ini -c custom.ini

Best,

-- 
Noah Slater, http://tumbolia.org/nslater