subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache subversion Wiki <comm...@subversion.apache.org>
Subject [Subversion Wiki] Update of "ServerDictatedConfiguration" by pburba
Date Tue, 03 Jan 2012 20:25:07 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Subversion Wiki" for change notification.

The "ServerDictatedConfiguration" page has been changed by pburba:
http://wiki.apache.org/subversion/ServerDictatedConfiguration?action=diff&rev1=28&rev2=29

Comment:
For now let's plan that no options can be overridden by well-behaved clients.

  
  There are a number of configuration options that existing Subversion users and administrators
might wish to have propagated from the server to the client.  The following is a list of the
specific options we are ''currently'' planning to implement (this list is obviously subject
to change):
  ||'''Configuration''' ||'''Scope''' ||'''Enforceability''' ||'''Notes''' ||
- ||auto-props ||per-directory ||Enforceable via hook scripts ||Non-overrideable by well-behaved
clients.||
+ ||auto-props ||per-directory ||Enforceable via hook scripts ||Non-overrideable by well-behaved
clients. ||
- ||ignores ||per-directory ||Enforceable via hook scripts ||Non-overrideable by well-behaved
clients.||
+ ||ignores ||per-directory ||Enforceable via hook scripts ||Non-overrideable by well-behaved
clients. ||
- ||store-plaintext-passwords ||per-repository ||Unenforceable ||Should it be possible to
override this without hacking the client? ||
+ ||store-plaintext-passwords ||per-repository ||Unenforceable ||Non-overrideable by well-behaved
clients. ||
  
  
  
@@ -121, +121 @@

  $
  }}}
  ==== Configuration hierarchy ====
- Server-dictated configuration will be the highest priority configuration recognized by well-behaved
Subversion clients, excepting per-use overrides (ala --config-option).  Only specific options
will be made available for server-dictated configuration though.  Also, only certain of the
server-dictated configuration options will be overridable at all.  These details will be governed
by hardcoded client-side whitelists.
+ As detailed in the behavioral specification matrix, only specific options will be made available
for server-dictated configuration. Server-dictated configuration will be the highest priority
configuration recognized by well-behaved Subversion clients.
  
  So, the order in which specific configuration options will be honored where found is:
  
-  1. Per-use overrides (--config-option) ''-- If permitted by whitelist''
   1. Server-dictated configuration
   1. Per-user runtime configuration (''${HOME}/.subversion''/*)
   1. The per-user Registry values (Windows Only)
@@ -143, +142 @@

   1. [[http://subversion.tigris.org/issues/show_bug.cgi?id=1973|Log Message Templates]].
   1. Reworking the client-side local configuration to support similar hierarchies of configuration.
 Today, the local configuration is largely universal in terms of remote scope -- changes to
the configuration apply to all working copies of all repositories on all servers.  (Some exceptions
exist in the 'servers' file, but those are largely disinteresting for our purpose.)  If the
client had access to hierarchical configuration, users could configure such things as "in
all working copies of ${ASF_REPOS_UUID}:/subversion, do not store pristines".
   1. Configuration options other than global-ignores, auto-props, and store-plaintext-passwords.
+  1. Allow well-behaved clients the ability to override ''some'' configuration options on
a per-use basis (i.e. using --config-option=FILE:SECTION:OPTION=[VALUE]).  Currently all planned
server dictated configs can only be overridden by a hacked client.  A mechanism to specify
which options are overrideable would also be required (e.g. hardcoded  client-side whitelists).
  
  === Related Issues ===
   * http://subversion.tigris.org/issues/show_bug.cgi?id=1974

Mime
View raw message