[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Repository-defined autoprops.

From: <kfogel_at_collab.net>
Date: 2005-05-27 22:29:06 CEST

SteveKing <steveking@gmx.ch> writes:
> Another idea comes to mind. Instead of using inherited properties, why
> not use a specially named config file stored in the repository?
> If per-directory isn't needed, a somewhat simpler solution could be:
> - if a file named e.g. .repoconfig is in stored in the repository
> root, then use this as the repository config file (same format as the
> config file now has).
> - After every update/checkout/... (operations that update the working
> copy) also fetch the config file
> - the config file is stored in a subfolder in the Subversion config
> folder (%APPDATA%\Subversion\repoconfigs\{repo-uuid} on windows for
> example).

This was exactly the proposal I wrote and then erased :-), yeah.

> Advantage:
> - easyer to implement (I think)
> - same format as the normal config file, so user already know how it works
> - only one copy of the configuration stored, not on each and every
> file/folder in the working copy as with inherited properties
> Disadvantage:
> - only per-repository, not per-folder (even though the config file
> could have sections for subfolders)

No need to have sections, it can just use paths.

However, one problem is that now everyone needs write access to a
global file. What if the projects do not trust each other, but still
share a repository?

> - to edit that file, one has to check out the repository root
> (non-recursively), edit the file and commit it

Better to have it in a subdirectory of the root. Greg Stein has a
great solution for this:

You put it in a subfolder named "/config". But, that's configurable,
via an svn:config-dir property set on the root directory of the
repository! So if people need to use "/config" for something else,
they can just set that property. Subversion would always look where
the property points; if no property, then default is "/config".

> - if a project already has such a file in the repository root stored,
> this change would break. Although I don't think that any project out
> there really has such a file stored there. If in doubt, the file could
> be named with a UUID.

See above about using a special property to redirect.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 27 23:07:37 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.