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

Re: [OT] Re: [BUG] The client can't use a different directory than .svn

From: Mike Mason <mgm_at_thoughtworks.net>
Date: 2003-12-12 15:13:30 CET

Ryan Hunt wrote:

> Well, I can't speak for others, but my needs for the "big WC needs to
> be shared" scenario is for multiple maintainers to be able to work on
> and maintain a tree of disk images which can be anywhere from
> 300MB-2GB each. Because of the size it doesn't make sense to have
> multiple WC's . I need access to it all of it all of the time because
> all of the disk images in the WC are going to be live and actively
> used by potentially as many as 500-1000 users simultaneously.

So, as a maintainer, can I simply check out the disk images I wish to
work on on a particular day? Do I really need to be able to see all of
those disk images at once? Can you organise the set of disk images into
different directories, allowing me as a maintainer to just check out a
subset of those images? Subversion keeps pristine copies of all the
files in a WC, so for a 200G disk on a workstation you can have 100G of
files checked out. That's 50 - 300 disk images.

By "live and actively used" does that mean they're going to be in use by
multiple processes on different machines at the same time? Will that
actually work? Are these virtual disks for VMware or something?

> In my case NAS snapshots were postulated as an alternative, however,
> this is not feasible due to the large amount of space this would
> require, and its inherent inflexibility. The specific features of SVN
> that are attractive in my situation are: cheap branching and copying,
> the ability to revert to any revision of a disk image, the ability to
> rapidly undo changes that were made using svn revert, and the ability
> to track changes made via the log mechanism.

I agree that snapshots are not quite what you want, but I also reckon a
WC with 500 users is not what you want either. Having binary files
checked into source control causes problems when multiple people change
them, because they cannot be merged, so you need some form of locking. A
single WC as the locking mechanism sounds like overkill though!


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 12 15:14:08 2003

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

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