You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Neel Banerjee <mr...@gmail.com> on 2006/11/21 22:31:48 UTC

Re: Single Checkout Area for Multiple Users

Hi,

I am thinking about implementing Subversion for source control of CAD files.
Many of the files that would need to be version controlled are large
binaries, and most people do not want to have to checkout individual copies
of the files locally.

Is it possible for multiple users to access and edit design data in a
location that has the data checkout from the repository?

Here a small example:
The repository exists on /path/to/repos.
An administrator ( or any user) checks out the data in the repository
file:///path/to/repos to /dev/proj. Multiple users " svn
add/change/delete/commit" the data in /dev/proj.

Is there a better way to handle this?

Thanks,
Neel

Re: Single Checkout Area for Multiple Users

Posted by Andy Levy <an...@gmail.com>.
On 11/21/06, Neel Banerjee <mr...@gmail.com> wrote:
> Hi,
>
> I am thinking about implementing Subversion for source control of CAD files.
> Many of the files that would need to be version controlled are large
> binaries, and most people do not want to have to checkout individual copies
> of the files locally.
>
> Is it possible for multiple users to access and edit design data in a
> location that has the data checkout from the repository?
>
> Here a small example:
> The repository exists on /path/to/repos.
> An administrator ( or any user) checks out the data in the repository
> file:///path/to/repos to /dev/proj. Multiple users " svn
> add/change/delete/commit" the data in /dev/proj.
>
> Is there a better way to handle this?

The better way is to have all users with their own working copy.

By sharing a single working copy, you're negating many of the benefits
of using a version control system. 2 users can clobber each others'
work. 2 users can work on different changes to the same file, and both
changes will be committed when one user commits, regardless of whether
the other user was ready or not. And any user can accidentally commit
any other user's changed files which weren't ready to be committed
yet.

Disk space is cheap, and you only need to check out the portion(s) of
the tree that you need to work on.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org