Background:
We've been coming up with support for cvs-like modules functionality
(roughly speaking: sparse directories) by virtue of a pair of scripts:
the first will checkout a "module" by doing a non-recursive checkout
of (say) /trunk, followed by non-recursive updates at intermediate
levels as needed, then normal (i.e.recursive) updates from there on
down.
A second script can be used to update a WC checked out with the first
by following breadcrumbs (files in .svn directories) left by the first
script, so that it can reproduce the pattern of non-recursive vs.
normal updates needed. Hope that makes sense. ( can include a fuller
example if that will help.
Problem:
If I take such a WC, and do a "svn copy . <URL>", the resultant copy
has *all* of /trunk, not just the partial tree I had extracted. I can
understand why this is, so my thought was to have a 3rd script that
follows the same bread crumbs but does svn copy operations.
Unfortunately (I just noticed) svn copy does not have a non-recursive
option. So...
Short-term solution:
I'm now thinking this copy-partial-tree script should cook up a second
WC recreating directory structure where needed, and issuing WC->WC
copies where needed. Does anyone have better ideas or foresee
problems with this approach?
Longer term:
I'm eagerly awaiting sparse directory support which (I think) will
make all this easier. However, I see that the notes here:
http://svn.collab.net/repos/svn/trunk/notes/sparse-directories.txt
do not mention the "svn copy" operation (or I missed it). So I'm
wondering what the intended behavior is for an svn copy of a sparse
tree?
Thanks,
Kylo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 19 04:14:58 2007