[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Bikeshed: configuration override order

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Fri, 6 Aug 2010 12:50:44 -0500

I'm doing some more thinking about repository-dictated configuration,
and one of the things I'd like some discussion on is the order of
configuration overrides. The consensus is that the repository can not
be sure that it's dictated configuration is received and respected by
the client, so it should treat whatever config it sends as purely
suggestive. We currently have several (implemented or proposed)
sources for configuration information, and I think they should be
searched in the following order:

 * 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.


Received on 2010-08-06 19:51:23 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.