Dear Wiki user, You have subscribed to a wiki page or wiki category on "Subversion Wiki" for change notification.
The "Inheritable-Ignores-AutoProps" page has been changed by pburba: http://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps?action=diff&rev1=7&rev2=8 Comment: Terminology tweak: Let's call this "repository dictated config" rather than "server dictated config". It's more accurate and it puts some separation from the aborted server-dictated config approach. ## page was renamed from InheritableAutoProps - == "Server Dictated Config" Via Inheritable Properties == + == Repository Dictated Configuration Via Inheritable Properties == Many software development shops of non-trivial size desire to have (and to the extent possible, to enforce) a uniform configuration environment among the various clients which commit to their repositories. Although these shops may have some ability to control the environment on the client machines (dictating software versions, etc), expecting humans to consistently set and maintain various runtime configuration parameters in accordance with corporate policy and on every repository-accessing client computer is both error-prone and unscalable. Subversion already provides the means of enforcing much (but not all) of this configuration through the hook script mechanism, but at best this can only punish non-compliant client behavior and clumsily recommend configuration changes (which, again, a human must implement on their client computer). An administrator could save a good deal of time and frustration if they could set a special configuration property on the root <<FootNote(Of course the property need not be set on the root of repository. It might be set on the root of some project folder, e.g. ^/subversion in our own repos, or some other root. The point is that the property doesn't need to be set on every directory to affect the whole repository (or some large subtree) the way that svn:ignore currently requires)>> of their repository which well-behaved clients (treating the special configuration property as inheritable) would use to override the user's local config file settings. @@ -9, +9 @@ {{{#!wiki note "Wait, this sounds familiar..." - There really isn't anything particularly "server dictated" about this design at all. It started life as an alternative approach to the server dictated configuration ideas described in http://wiki.apache.org/subversion/ServerDictatedConfiguration and as such a quick read of that original design is suggested. If you've already read that a lot of this will sound familiar since the goals are essentially the same. + This effort started life as an alternative approach to the server dictated configuration ideas described in http://wiki.apache.org/subversion/ServerDictatedConfiguration and as such a quick read of that original design is suggested. If you've already read that a lot of this will sound familiar since the goals are essentially the same. }}} === Behavioral Specification === New Subversion reserved properties with the prefix "svn:inheritable-*"<<FootNote(Prefer "svn:config-*" or some other option? Don't worry, it's not too late to paint the bike shed a new color)>> will provide additional configuration information that overrides/extends the settings found in the user's run-time configuration. Initially there will be two such properties "svn:inheritable-auto-props" and "svn:inheritable-ignores".
