[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: Michael Stillwell <mjs_at_beebo.org>
Date: 2007-11-09 15:56:49 CET

On Nov 9, 2007 2:00 PM, Andy Levy <andy.levy@gmail.com> wrote:
> On 11/9/07, Michael Stillwell <mjs@beebo.org> wrote:
> > Is it possible/safe to "share" a checked-out project amongst users?
> > For example if usera does:
> >
> > $ cd /usr/www/project
> > $ svn co --username usera --password blah http://svnserver/project/trunk .
> >
> > Can userb perform svn operations on the same /usr/www/project
> > directory (so long as they have permissions to write to the individual
> > files)?
> >
> > I thought the fact that usera did the initial checkout might be stored
> > somewhere in the .svn directories, but this doesn't seem to be the
> > case, and so it seems like:
> >
> > * checked out projects are user-independent in the sense that
> > * svn doesn't know (and doesn't need to know) which user did the
> > checkout in the first place
> >
> > Is this correct?
> >
> > Also, are svn operations locked, or will it be a problem if usera and
> > userb do a update at exactly the same time?
> 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.

Does it help if these multiple logins are only used to update, not
commit? We're actually trying to move from a situation where a
single, shared account (shared Unix account, and shared svn account)
has been used to update the working copy (the working copy is a live
website) to a situation where individual developers update the live
website from their own private accounts. (i.e. to increase
accountability, not decrease it.)

Is there a recommended way to do this? We don't really want to use
rsync, cp, etc. to copy a working copy into the live web
directory--this would seem to introduce a lot of unnecessary work and
complexity since "svn up" does 95% of what we want. And updating via
a commit hook (i.e. completely automated) is a bit fussy and
inflexible for the projects we work on.


+44 78 2118 9049
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 9 15:57:27 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.