RE: Seeking recommendations on sharing Subversion config within a development team

From: Timothy Astle [mailto:timothy.astle_at_caris.com]
Sent: Tuesday, January 24, 2012 6:02 AM
To: Nico Kadel-Garcia
Cc: users_at_subversion.apache.org
Subject: Re: Seeking recommendations on sharing Subversion config within a development team

We mainly use Windows for development, so I'm thinking more about sharing the %APPDATA%\Subversion\config file. (Which if I recall correctly is the same as the $HOME/.svn/config on a *nix system.)

I'm okay with sharing the entire directory contents or just a single file. Since we have a team of about 50 developers, it'd be really beneficial to keep everyone up to date. Maybe it's just as simple as having the system administrators push out updates to everyone's system.

Has anyone tried to tackle this problem before I possibly go re-invent the wheel. :)

Tim

---
I wrote a script that engineers use to download a build's binaries and integrate them into their source tree. The first step of this script is to fetch (from Svn of course) the latest config file, compare it with the one in the user's folder, and offer to overwrite it if it is different. If the user changed the script on their end, their changes could get lost, but I didn't want to version the folder containing the config file.
Occasionally we have users who fail to use even this script, so it's not a perfect solution, but it works reasonably well.
Oh, and the build download script is in a versioned folder and it checks whether its folder is current, and if not, offers to update itself as well.
Svn makes it a breeze to write self-updating scripts.
--Todd
________________________________
Please consider the environment before printing this e-mail.
The contents of this e-mail message (including any attachments) are confidential to and are intended to be conveyed for the use of the recipient to whom it is addressed only. If you receive this transmission in error, please notify the sender of this immediately and delete the message from your system. Any distribution, reproduction or use of this message by someone other than recipient is not authorized and may be unlawful.