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=11&rev2=12 Comment: Some more wording tweaks to account for recent inheritable property name change. 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:auto-props" and "svn:global-ignores". + Two new Subversion reserved properties, "svn:auto-props" and "svn:global-ignores", will provide additional configuration information that overrides/extends the settings found in the user's run-time configuration. This "svn:auto-props" property will (no surprise!) override/extend the auto-props configuration settings which dictate the properties which are automatically set on newly added or imported files. Unlike traditional auto-props, which can be disabled in the run-time config (i.e. "enable-auto-props = no"), svn:auto-props cannot be disabled by a well-behaved client. @@ -23, +23 @@ {{{#!wiki warning "Well-Behaved Clients" and "Trust, But Verify" - The configuration dictated by the "svn:inheritable-*" properties can at best be only a suggestion to the client. Older clients will obviously not understand the meaning of these properties and as open source software it is relatively easy for a malicious user to modify a client to ignore these special properties. Given this reality, server-side enforcement of desired behaviors (where possible, and often via hook scripts) is still strongly recommended. + The configuration dictated by the "svn:auto-props" and "svn:global-ignores" properties can at best be only a suggestion to the client. Older clients will obviously not understand the meaning of these properties and as open source software it is relatively easy for a malicious user to modify a client to ignore these special properties. Given this reality, server-side enforcement of desired behaviors (where possible, and often via hook scripts) is still strongly recommended. The new "ephemeral transaction properties" feature (see http://subversion.tigris.org/issues/show_bug.cgi?id=4124) provide a simple way for servers to disallow commits from clients which don't understand svn:auto-props. Thus there is no new capability string required for this feature. }}} @@ -42, +42 @@ 1. svn:auto-props inherited from a nearer parent override those from a more distant parent. 1. Explicit svn:auto-props override inherited auto-props. - Auto-props are overridden by individual file pattern. This means the if a run-time config defines auto-props for several different file patterns (say *.c, *.h, and *.py) and a single pattern (*.c) is defined in a svn:inheritabled-auto-props property at the root of the repository, then only the *.h and *.py auto-props from the run-time config still apply, only the *.c value is overridden. + Auto-props are overridden by individual file pattern. This means the if a run-time config defines auto-props for several different file patterns (say *.c, *.h, and *.py) and a single pattern (*.c) is defined in a svn:auto-props property at the root of the repository, then only the *.h and *.py auto-props from the run-time config still apply, only the *.c value is overridden. For example if we have this run-time config: @@ -117, +117 @@ There is no actual hierarchy among these ignore sources, the patterns found in each are simply combined, they do do not override each other. If a subcommand is passed the --no-ignore option, then #1 and #3 are not considered. {{{#!wiki warning - Remember that users can only inherit properties from paths which they have read access to -- see http://wiki.apache.org/subversion/InheritedProperties#Authentication. So make sure all users have read access to the path(s) on which you set svn:inheritable-* properties. + Remember that users can only inherit properties from paths which they have read access to -- see http://wiki.apache.org/subversion/InheritedProperties#Authentication. So make sure all users have read access to the path(s) on which you set "svn:auto-props" or "svn:global-ignores" properties. }}}
