I've encountered a few anomalies regarding the sparse workaareas and externals. 
 I can construct a sparse workarea using either a top down approach or a 
bottoms up approach as shown in the following examples

Top down:

$ svn co -depth immediates <URL> modules
A modules
A modules/module1
A modules/module2
$ svn update -set-depth immediates modules/*
A modules/module1/subdir1
A modules/module1/subdir2
A modules/module2/subdir1
A modules/module2/subdir2
$svn update -set-depth infinity modules/*/subdir1
A modules/module1/subdir1/file1
A modules/module2/subdir1/file3

Bottoms up:

$svn co <URL> modules
A modules
A modules/module1
A modules/module1/subdir1
A modules/module1/subdir1/file1
A modules/module2/subdir2
A modules/module1/subdir2/file2
A modules/module2
A moduels/module2/subdir1
A modules/module2/subdir1/file3
A modules/module2/subdir2
A modules/module2/subdir2/file4
A modules/external1/subdir1
A modules/external1/subdir1/file5
A modules/external1/subdir2/
A modules/external1/subdir2/file6
$svn update -set-depth empty modules/*/subdir2
D modules/module1/subdir2/file2
D modules/module2/subdir2/file4
D modules/external1/subdir2/file6

If it weren't for the external, the result is the same.  Unfortunately the 
initial checkout of an external appears to be an all or nothing scenario 
requiring a depth of infinity.

The disadvantage of a bottoms up approach is that I'm checking out everything 
from the repository into the workarea and them pruning it back.  In my actual 
case, I'm dealing with 10's of thousands of file and this process can take 
nearly 3 hours.

The ideal solution would be a top down approach that handled externals 
identically to modules from the local repository.

Any suggestions?

Dave Andreas












This message (including any attachments) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law or may constitute as attorney work product.  If 
you are not the intended recipient, you are hereby notified that any use, 
dissemination, distribution, or copying of this communication is strictly 
prohibited. If you have received this communication in error, notify us 
immediately by telephone and (i) destroy this message if a facsimile or (ii) 
delete this message immediately if this is an electronic communication.  

Thank you.

Reply via email to