Re: [Monotone-devel] [bug #29576] mtn tries to rewrite options file every time

[Thomas Keller]

Am 18.04.10 00:57, schrieb Thomas Keller:
> Am 18.04.10 00:48, schrieb Derek Scherger:
>> On Sat, Apr 17, 2010 at 6:34 AM, Thomas Keller <address@hidden> wrote:
>>
>>>
>>> This is only partially a problem of the hook. The options system simply
>>> has no general code to accept --no-<something> options which would
>>> switch the default of the --<something> value to the opposite.
>>>
>>
>> Allowing a general --no-foo for each boolean option --foo would probably be
>> a good thing though. It would be nice if any early --no-files option could
>> be overridden by a later --files option. Ditto for --no-merges --no-graph,
>> etc. This may not make sense for every boolean option that we have, but it
>> would for many of them.

One thing I forgot here - we need to decide what we do with boolean
options which already have a "no" in their name, but whose names cannot
be easily switched to the opposite without breaking BC, f.e. "--norc".
"--no-norc" sounds stupid, but maybe we could emulate that in the
options code and expand a "--no<something>" to "--no-<something>" and
then continue as usual (i.e. by also providing an --rc option)...?

Thomas.

-- 
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

signature.asc
Description: OpenPGP digital signature