mike nicholaides wrote:
> Hey guys,
>
> I hope y'all can help me out. I've been googling and reading the
> archives of this list for about a week now.
>
> I have a huge intranet project that I want to put under version
> control. The problem I've run into is that the whole project is 1.3
> GB, which means that checking out the whole project, even on the same
> machine as the repository, takes forever.
>
> Checking out sub directories won't work, because they rely on the
> parent directories. Non-recursive checkouts of directories doesn't
> work either, because I can't recursively commit from a non-recursive
> checkout.
>
> Here's a simple example of what I want to do, in case the previous
> paragraphs are vague.
>
> I have a directory structure:
>
> trunk/
> tools/
> common/
> hammer/
> drill/
> chisel/
> custom/
> cde24/
> abc92/
> customers/
> projects/
> ...
>
> Now, say I want to work in "drill" directory. The project depends on
> files in the parent, grandparent and ancestor directories.
>
> So, I want my check out to look like:
> trunk/
> tools/
> common/
> hammer/
> And, I want trunk, tools, common, and hammer to have all their files
> checked out, but none of the directories (except hammer should have
> all child directories checked out).
>
> Does this make sense at all?
>
> What do I do?
Standard advice is to do the initial checkout (which, as you say, will
be fairly hefty); after that point, you shouldn't need to do any full
checkouts again--just updates, switches, etc., which will all be fairly
fast.
Alternatively, you could do a non-recursive checkout and then update
each sub-folder individually, spreading the network load across several
commands, but this obviously requires more baby-sitting.
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 28 19:52:01 2006