Issue 1974

Hi all,

Having no time to become fully registered, please submit the attached to
Issue 1974, refer to it or forget...

Sorry for ^M 's in the file.

Regards,
Radomir Zoltowski

-- 
_________________________________________________________
 Radomir Zoltowski <Radomir.Zoltowski_at_s3group.com>
 Applications Engineer
 Silicon & Software Systems Ltd., IT Department
 South County Business Park, Leopardstown, Dublin 18, IRELAND
 Tel.: +353 1 291 1224, Fax: +353 1 291 1001
_________________________________________________________
The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s).
Please direct any additional queries to: communications_at_s3group.com.
Thank You.
Silicon and Software Systems Limited. Registered in Ireland no. 378073.
Registered Office: South County Business Park, Leopardstown, Dublin 18

Issue 1974

All,

Let me just jump into the conversation. As an admin (not a day2day user) I would welcome the per-repository configuration of course.

Logically, the full repository access addres is generally composed as:
proto://user:password_at_host.domain/location/repository

We can have single config per protocol, as we can configure behaviour of svnserver, ssh, http server (Apache) through respective config files. We can configure behaviour per users through naming services restrictions and svn client configuration. We can get a single config for host.domain as per server system-wide svn configuration as well. The only remaining component is the repository. We cannot get a single config per-repository.

It's like having 4 limbs, with only 3 moving.

Now, the development is an interesting part, as with FSFS there is no server. Yet, an svn client having remembered repository location, would also remember potentially a relative subdirectory of repository config files. It then should be able to cache them and re-read them "every so often" or read them "always".

Additionally, a discussion about default/mandatory could be immediately solved by placing two config files: *default*.cfg and *mandatory*.cfg. This is actually how Mozilla/Firefox works with prefs.js and user.js, easy to predict without reading.

Just a philosophical bit...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-07 18:48:07 CEST