You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Daniel Patterson <da...@adaptiveinternational.com> on 2003/07/03 23:59:10 UTC
Re: [Issue 1385] New - "make check" tests fail if on modified
~/.subversion/config
On Fri, 2003-07-04 at 09:42, Branko Čibej wrote:
> mark benedetto king wrote:
> >I believe that virtually every configurable option probably deserves
> >some command-line tweakability. The fact that it is configurable means
> >that not everyone wants the same thing; this is likely to also mean
> >that one person might not want the same thing all of the time.
> >
> Yikes. I'd only support this if the config option parsing could be
> hoisted off of the svn_config interface itself. Actually defining
> explicit command line options for each and every option is a huge can of
> worms.
I don't know whether this discussion is heading down this path or not,
but perhaps a config file format change might better support
this kind of thing? Time to get out the bikeshed-painting brushes...
A good (my bikeshed) model for this that I've seen is the
configuration used by "apt" in Debian. And I quote:
Syntacticly the configuration language is modeled after what
the ISC tools such as bind and dhcp use. Each line is of the form
APT::Get::Assume-Yes "true";
The trailing semicolon is required and the quotes are optional.
A new scope can be opened with curly braces, like:
APT {
Get {
Assume-Yes "true";
Fix-Broken "true";
};
};
......
All of the APT tools take a -o option which allows an arbitary
configuration directive to be specified on the command line. The
syntax is a full option name (APT::Get::Assume-Yes for
instance) followed by an equals sign then the new value of the
option. Lists can be appended too by adding a trailing :: to the
list name.
For example, I regularly override the proxy cache control by doing:
apt-get -o acquire::http::proxy::no-cache="yes" install subversion
All the options are settable this way.
The parser for this config file is reasonably trivial (I remember
hearing in the order of 300 lines) and is extremely flexible.
daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 1385] New - "make check" tests fail if on
modified ~/.subversion/config
Posted by Daniel Patterson <da...@adaptiveinternational.com>.
On Fri, 2003-07-04 at 10:03, Branko Čibej wrote:
> No no no. Our config file format is compatible with Pythons ConfigParser
> class. This was done on purpose, and I wouldn't want to change that. And
> we don't need more than one level of scoping in the config files, IMHO.
Ah, that makes sense. I guess a command-line syntax to arbitarily
control the configuraton data would be all that's required then.
daniel
--
Signature at: http://www.mel.au.adaptiveinternational.com/~danpat/signature.txt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 1385] New - "make check" tests fail if on modified ~/.subversion/config
Posted by Branko Čibej <br...@xbc.nu>.
Daniel Patterson wrote:
>On Fri, 2003-07-04 at 09:42, Branko Čibej wrote:
>
>
>>mark benedetto king wrote:
>>
>>
>>>I believe that virtually every configurable option probably deserves
>>>some command-line tweakability. The fact that it is configurable means
>>>that not everyone wants the same thing; this is likely to also mean
>>>that one person might not want the same thing all of the time.
>>>
>>>
>>>
>>Yikes. I'd only support this if the config option parsing could be
>>hoisted off of the svn_config interface itself. Actually defining
>>explicit command line options for each and every option is a huge can of
>>worms.
>>
>>
>
> I don't know whether this discussion is heading down this path or not,
> but perhaps a config file format change might better support
> this kind of thing? Time to get out the bikeshed-painting brushes...
>
No no no. Our config file format is compatible with Pythons ConfigParser
class. This was done on purpose, and I wouldn't want to change that. And
we don't need more than one level of scoping in the config files, IMHO.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org