Configuration area in the repository

I see that there's a configuration area for each machine (e.g. /etc/...) and in the user's home directory.

It would be nice to have one per-server, or per repository (better, and probably simpler) too.

The reason being: I want to set global-ignores, and automatic property settings (e.g. mime-type) *but* I don't want to force developers to manually keep their configuration areas up to date.

This could work by having a special set of properties on the root of the repository, or having a special directory at the root of the repository. The format of data here would match existing configuration areas. This data would be placed into the working-copy on each update, just like anything else.

Probably the system and per-user configuration areas would over-ride repository settings?

Is this a good idea? How else might one accomplish this? I thought of post commit triggers, but they can't modify the transaction, and I don't think server-side propsets are implemented yet (and besides, that would just run the post-commit hook again this causing an endless loop, wouldn't it?)

--
Stephen Warren, Software Engineer, Parama Networks, San Jose, CA
http://www.wwwdotorg.org/work_contact/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org