> * Client site-wide configuration (/etc/subversion)
> * Client user-specific configuration (~/subversion, 'svn --config-
> dir')
> * Repository-dictated configuration (as described above)
> * Explicit configuration supplied by the client application
> ('svn --config-option', or Eclipse configuration options)
>
> Not every location contains every bit of config, of course, but in
> the
> case of conflicts, the most recent encountered value sticks. In
> other
> words, a client could override repository-dictated configuration
> options by using 'svn --config-option', or the (as yet
> unimplemented)
> equivalent facility for other API consumers.
>
> Thoughts?
Hmm... so you are saying that repository settings will override locally
configured settings but not CLI specified settings? Why? That seems a bit
backward to me. I would expect:
* Repository-dictated configuration (as described above)
* Client site-wide configuration (/etc/subversion)
* Client user-specific configuration (~/subversion, 'svn --config-
dir')
* Explicit configuration supplied by the client application
('svn --config-option', or Eclipse configuration options)
Can these settings be path specific in the repository? What happens if I have
checked-out a sub-path... I'm not sure if you plan on implementing this as a
config file a user can check into svn or as properties like the keyword stuff
or were you thinking that these is info that will be passed from the server to
the client when requested?
One other option, an idea that ASP.Net uses for its config settings is the
ability to specify at what level a setting can be overridden.
BOb
