On Apr 28, 2006, at 19:44, mike nicholaides wrote:
> 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.
Is that really true of non-recursive checkouts? I wasn't aware of
that. I'm not sure why that would be....
You could check out the entire project (takes a long time, sure),
then "svn switch" the directories you don't need to an empty
directory somewhere in the repository, possibly created for just this
purpose. This then makes the working copy smaller again, makes "svn
status" faster again because there are fewer directories, and so forth.
If many people will often need the same subset of the project, you
could do this once, then make it available via Samba or web site or
FTP or whatever where people can download this pre-made partial
checkout, and then do an "svn update" on their local copy to get it
up-to-date again. You could automate a task which makes the
downloadable pre-made partial checkout update itself periodically so
it's not too stale when it's downloaded. If there are multiple such
subsets that people would want, you could make several such pre-made
working copies available for download.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 28 23:11:58 2006