Ben Collins-Sussman wrote:
> Well, users have been asking for server-settings that can be broadcast
> to clients for quite a while now.. I guess we've ignored the request
> long enough to the point that other projects have started improvising
> workaround solutions. :-/
As a sidenote: yes, this has come up on both dev@ and users@ list quite
often. When an issue got filed and I added some comments about having
custom config options, this was rejected right away - so I couldn't wait
for that to happen soon (if ever).
btw: the issue I'm talking about is 1974
http://subversion.tigris.org/issues/show_bug.cgi?id=1974
About how I think this could be done without breaking older clients at all:
define a file named 'svnrepoconfig' which resides in the repository
root. It's treated like a normal file, unless it's
1. located in the repository root
2. has a special new svn property set (e.g. svn:repoconfig = yes)
If those are true, then it's not a normal file anymore but one that
get's transferred on every update/commit. The client will store it
inside the config area, maybe in a subfolder called 'repoconfigs' right
beside 'auth' folder.
To reduce the data traffic, that file could even be 'versioned' like
other working copy files, with the difference that it's stored in the
config area.
That way,
- older clients won't break
- with mod_authz_svn you can set the access rights so that not everyone
can change those settings
- you don't need to contact the repository to get the configs - they're
stored locally so every client can access them immediatley if needed.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 13 17:56:12 2005