RE: Bikeshed: configuration override order
From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Fri, 6 Aug 2010 14:28:11 -0400
> On Fri, Aug 6, 2010 at 1:13 PM, Greg Hudson <ghudson_at_mit.edu>
As I said in a previous email, you might want to consider looking at the asp.net configuration and how that is done. They have a configuration hierarchy and inheritence. You can specify the scope of the configuration items and also you can restrict inheritence on certain items.
Of course, since svn is open source... it would be possible to create a client that would ignore inheritance restrictions with a few // characters in the source code. I guess an enterprise client would want to compile there own client and sign it and only allow signed clients to access the repository or something to mitigate that kind of stuff.
But really why do people want this. I think it is so some settings like auto-props and other things that need to be set for a specific project will take place without having to distribute a config or send an email with "make sure you add this to your config" type of warning from a pre-commit hook that notices certain properties are missing for certain file types.
This is an archived mail posted to the Subversion Dev mailing list.