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



On 24/01/2012 12:02 AM, Nico Kadel-Garcia wrote:
On Mon, Jan 23, 2012 at 2:22 PM, Timothy Astle<timothy.as...@caris.com>  wrote:
Does anyone have any recommendations for sharing the Subversion config file
to a team of developers?

I'd like to be able to ensure that all of the developers always have the
latest corporately-approved configuration.
Individual config files, s in $HOME/.svn config files? Or a Subversion
published configuration for development environments?

--
Timothy Astle, BCS
Web Development Manager

*CARIS* <http://www.caris.com>
115 Waggoners Lane
Fredericton, New Brunswick
Canada    E3B 2L4
Tel: +1.506.458.8533     Fax: +1.506.459.3849
www.caris.com <http://www.caris.com>

*Join us for CARIS 2012 --- Exploration and Discovery*
June 25--28, 2012, Vancouver, British Columbia, Canada
Visit www.caris.com/caris2012 <http://www.caris.com/caris2012> for details today

*Connect with CARIS*
Twitter <http://www.twitter.com/CARIS_GIS> | LinkedIn <http://www.linkedin.com/groups?mostPopular=&gid=3217878> | Facebook <http://www.facebook.com/pages/CARIS-The-Marine-GIS-Experts/123907500987669?v=app_4949752878> | YouTube <http://www.youtube.com/user/CARISGIS>

Download your free copy of CARIS Easy View today!
www.caris.com/easyview <http://www.caris.com/easyview>

_________________________________________________________________________
This email and any files transmitted with it are confidential and intended only for the addressee(s). If you are not the intended recipient(s) please notify us by email reply. You should not use, disclose, distribute or copy this communication if received in error.

Any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of the company. No binding contract will result from this email until such time as a written document is signed on behalf of the company.

Reply via email to