On 2004-03-31 21:27:26 +0200, Lele Gaifax wrote:
> >>>>> "Dominic" == Dominic Anello <email@example.com> writes:
> Dominic> Sorry if this has been proposed before, but what about
> Dominic> making the per-repo config a property (eg svn:config) of
> Dominic> the repo root directory? Then you wouldn't have to worry
> Dominic> about collisions with local files.
> A viable alternative, although this only allow to /mandate/ some
> settings, since a property have to be committed and this imply that
> everyone's forced to use those settings within that context. As for
> the API, "svn propedit" is already there :-)
> OTOH, it suffers of the same problem raised by John, ie how to "spread
> down" the settings so that a user that checks out just a portion of
> the repository will acquire the same options.
Handle it like auth caching is currently handled. It could be placed in
Then it just becomes part of the merged config tree:
command line switches -> ~/.subversion/config
-> ~/.subversion/conf/<repo-uuid> -> /etc/subversion/config
Where "->" means "overrides". I think the main hurdle would be that
there would need to be some method to tell the client it needs to update
its per-repo config.
Security would probably have to be handled by a pre-commit hook - only
allow "admin" users to commit changes to svn:config.
So, I've made peace with the falling leaves. I see their same fate in
my own body. But I won't be frightened when I am awoken from this dream
and returned to that which gave birth to me.
-Bright Eyes, "Method Acting"
Received on Wed Mar 31 22:33:10 2004
- application/pgp-signature attachment: stored