On Nov 4, 2005, at 08:51, Robert Swarbrick wrote:
> Rather than simply checking out svn://myserver/software/trunk as a
> whole, check it out non-recursively, then individually check out the
> sub-folders you want on that client.
>
> I believe "svn update" will then only update them (minor testing here
> appears to confirm this).
>
> For everything except groupG and projectE it would look like this.
> The
> "-N" is the important bit.
>
> svn checkout -N svn://myserver/software/trunk config1
> cd config1
> svn checkout svn://myserver/software/trunk/projectA
> svn checkout svn://myserver/software/trunk/projectB
> svn checkout -N svn://myserver/software/trunk/groupC
> cd groupC
> svn checkout svn://myserver/software/trunk/groupC/projectD
> svn checkout svn://myserver/software/trunk/groupC/projectF
>
> "svn update" from the root dir of all of this will only update the
> checked out trees.
>
> This does mean that if someone adds in "projectF2" to "groupC" you
> won't
> get it automatically, but given your requirement of "different
> machines/developers need different code" that's presumably desired.
>
> If developers find themselves checking out a whole new tree often then
> dropping the above in a script may be useful, also possibly storing
> the
> scripts elsewhere in subversion under suitable names so anyone can
> check
> out a particular configuration.
svn checkout -N is broken and has been forever:
http://subversion.tigris.org/issues/show_bug.cgi?id=695
I believe someone is working on fixing it. Until then, use with caution.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 4 14:22:12 2005