Phillip Rhodes <mindcrime_at_cpphacker.co.uk> writes:
> John M. Black wrote:
>> We have a situation exactly like this. We simply instruct people
>> not to just check out "trunk", but instead check out the specific
>> projects they need "trunk/project".
>>
>> Those of us who use command line use batch files to update each repo
>> found within the trunk WC folder.
>
> Yeah, looks like writing a script to do the updates is the solution I
> want, if there's no easy way to do this natively with SVN. Since I
> use
> a script to do the checkout now, changing from checking out trunk to
> checking out the individual modules is easy enough. And the script you
> mention works around the problem of folks having to run svn up multiple
> times from the command line, in order to get updates.
The upcoming --depth feature ("sparse checkouts" or "sparse
directories") will support what you need, but you'll probably want
wrapper scripts to invoke the right series of commands to construct the
sparse working copy.
http://subversion.tigris.org/svn_1.5_releasenotes.html#sparse-checkouts
has more details.
Remember, this isn't available until 1.5 comes out, unless you want to
use trunk or the pre-release testing distributions (which we encourage
as long as you're comfortable using beta software).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-23 05:57:05 CET