[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Shared working copy

From: John Waycott <javajohn_at_cox.net>
Date: Sun, 21 Jun 2009 07:09:20 -0700

On Jun 19, 2009, at 7:04 AM, Michael Miller wrote:

> I'm looking for feedback from anyone who might have worked with or
> can provide the pros & cons of multiple developers using a shared
> working copy.
> This process was proposed to solve some issues with a development
> group that maintains a vendor package (mostly COBOL) with many
> generated items and a unique build process.
> I've provided some reasons why this is may not work, but being
> relatively new to Subversion I would like some feedback from more
> experiences users.

I've never seen sharing a WC work well in practice. Developers start
to step on each other's toes and changes can be irrevocably lost if
there isn't constant communications (minute-by-minute) between the
developers. A shared WC might work using a locking model, but then you
run into other problems.

Sometimes developers propose a shared WC because the build environment
is too complex to set up on each developer's workstation. As others
have stated, a shared build machine can solve that problem.

It would be good to understand exactly what problem you want to solve.
There are usually better ways than sharing a WC.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-21 16:10:29 CEST

This is an archived mail posted to the Subversion Users mailing list.