On Tue, Dec 21, 2010 at 12:34 AM, Blair Zajac <blair_at_orcaware.com> wrote:
> On 12/20/10 8:30 PM, C. Michael Pilato wrote:
>> On 12/20/2010 05:28 PM, Hyrum K. Wright wrote:
>>> In issue #3765, I suggest the possibility of a CVS-style config file
>>> wherein a user could specify a set of default arguments for a given
>>> subcommand. For example, 'svn diff' would default to 'svn diff -x -p'
>>> if the config file had an entry for such. Thinking this would be an
>>> SMOP, I jumped in...only to discover that it isn't.
>>> The actual implementation isn't hard, I'm just wondering about where
>>> the configuration should live. We have a ~/.subversion/config file,
>>> but these options aren't for the client library, they are specific to
>>> the commandline client. This makes me think that we should have a
>>> separate file for the commandline client, and that it may want to be
>>> something like ~/.svnrc or something equally commandline-ish.
>> ~/.svnrc makes perfect sense to me (with /etc/svnrc as a system-wide
>> default, if you wanna roll that way).
> What about ~/.subversion/cli or ~/.subversion/command-line-client. If
> somebody wants to copy an existing configuration from another user, they
> just can't copy ~/.subversion now.
There a chicken-and-egg problem with using ~/.subversion (and it's
other-platform equivalents). We have a commandline arg which allows a
user to specify, at runtime, the configuration directory to use. In
order to see this arg, we have to parse the comandline arguments. It
becomes rather more convoluted if we parse some of the arguments to
determine the config directory, and then add more arguments *based* on
that config directory.
Also, I agree with the other point that everything in ~/.subversion is
libsvn_client (or lower), and since this is strictly a commandline
client feature, it should go in a separate location.
Received on 2010-12-22 14:39:20 CET