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

general source control strategy for many projects and many developers

From: Ryan Jarvis <ryan_at_muzzylane.com>
Date: Thu, 03 Jan 2008 10:20:35 -0500


I asked this question on irc but didn't get a definite yes or no. I'm
looking to determine a particular strategy as my office expands the
number of projects needed to be under source control.

On the server, I would like to have a bunch of source dirs like "calc",
"calendar", "spreadsheet" etc. with the trunk, tags and branches
subfolders underneath.

I would like my end-users to create a project dir called "projects" on
their local development machines and inside it only checkout the source
dirs that are currently relevant to them. For example, "calc" and

Now, the process for my end-users I want to be the same: using
TortoiseSVN or equivalent, they run the commands 'update' and 'commit'
on the "projects" dir only, not on any source dir underneath it. During
the update, I want their projects dir to only pull down the changes to
the source dirs they have currently checked out. During the commit, I
want all changes in all their source dirs to be checked in as a single

Is this situation possible out of the box? Could it perhaps be
possible if I wrote some python scripts the my end-user would call
instead of svn commands directly?

The two approaches I have tried so far do not meet my needs. If I put
all my source dirs under one folder on the server, end-users end up
checking out everything when they update. Some source dirs (i.e.
"calendar") may contain 100+ mb of binaries that I do not wanting tying
up their bandwidth if those source dirs are not currently relevant to
them. They could still check out source dirs individually from this
single folder, but then they can't run an update or commit command from
their project dir, they have to run them individually on their source
dirs inside the project dir. The second approach would be to have each
source dir its own root, but then my users cannot commit changes to
multiple source dirs as a single revision. Currently, each revision
increment in our setup corresponds to a single conceptual change (i.e. a
simultaneous change in both "calc" and "spreadsheet" may constitute a
Feature) and as we expand I would like to keep it that way.

Any thoughts on this would be greatly appreciated. Thanks.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-03 20:01:51 CET

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.