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

RE: sharing a checked-out project amongst users

From: Miller, Eric <Eric.Miller_at_amd.com>
Date: 2007-11-09 16:58:43 CET

> Just don't do it. Sharing a working copy between users, aside from the
> permissions headaches, negates many of the good things that using
> version control provides - accountability & insulation from others to
> name but two.

Just a note - I don't see how it negates accountability. Commits are
still logged per user yes? Working copy fud edits are visible via file
owner yes?

Sometimes you have to do it. But like Andy I'd say avoid it if you can.

One such case is where you have huge amounts of data having separate
working copies for each user would be insanely inefficient for both disk
space and bandwidth.

One problem with shared working copies is that when meta-data lock turds
are left around (due to aborted updates/commits/who knows) there needs
to be good communication to make sure those locks are really stale and
not the result of someone currently running a command.

Lastly - subversion's working copies just aren't robust enough to be put
in a multi-user working copy situation and the client isn't very adept
at fixing issues. Sometimes it can get so messed up the only solution
is to "remove your working copy and checkout a new one", which may not
be feasible for you as it would impact many users instead of just one.

Just some food for thought.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 9 17:03:12 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.