RE: Bikeshed: configuration override order
From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Mon, 9 Aug 2010 17:11:11 -0400
> Stefan Küng wrote on Sat, Aug 07, 2010 at 12:59:26 +0200:
A repository administrator already has a way to enforce stuff like this via pre-commit hooks. Isn't that satisfactory. Wouldn't having repository/service specified settings just make it easier for devs so they don't have to worry about stuff like this to match every repository they deal with?
Perhaps make enforcing certain auto-props and other possible client settings that affect what is more of a config thing rather than needing to write hook scripts is enough.
There are two issues here...
1. The repo admin wants to enforce what is commited to their repo. This exists with scripts but common request can be made inherient repo settings (probably need to be path based).
2. The admins want to simplify config for clients committing to repos that have various enforcements made (see item 1) without needing to deal with distirbuting client config files or what have you.
If these remain separate there is not way a client could over ride the repo admins whishes even if they did build there own client exe that overrode any repo config since it would be enforced via item 1.
This is an archived mail posted to the Subversion Dev mailing list.