[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Is it possible to do a "partial" or a filtered checkout

From: Carsten Koch <Carsten.Koch_at_icem.com>
Date: 2005-07-11 22:09:31 CEST

Tor Ringstad wrote:
>>The solution here is to not check out dir2 in the first place,
>>i.e. instead of your initial
>> svn co file:///c:/svn/Repositories/Test/trunk SVNTest
>>you would do a
>> svn co -N file:///c:/svn/Repositories/Test/trunk SVNTest
>> cd SVNTest
>> svn update dir1
> Nope! The "-N" option is broken, and won't work as well as you wish.
> It may seem to work for a short while, but then suddenly the wc will
> blow up in your face.

can you describe that in more technical terms? ;-)

So far, I have been using "svn checkout -N" for a few days
and it works as expected.

Can you please describe a real step-by-step test case that fails?

> This is a well documented bug (issue #695) that has existed for
> several years:
> http://subversion.tigris.org/issues/show_bug.cgi?id=695
> If you, against my belief, are able to get the "-N" option to work in
> any kind of seemingly reliable way, I'd be very interesting in hearing
> what your typical work-flow is like.

We are in the process of converting our SCM system for various
ICEM products from CVS to subversion.
Some historic directory structures with up to 800 source files
in one directory must be preserved (the management does not
assign sufficient priorities for a cleanup).
Some build tools also require that you check out directories
above the ones you are working in, but obviously you only want
that branch of the directory tree, not the entire tree.

I personally believe that 800 source files in one directory is
a crime. But it is a crime that I did not commit.

As much as I would like to, I do not have the power to change that.

So I am the poor guy who has to make subversion work for those
who invented all the mess described above. ;-)

Anyway, I wrote a number of python scripts (using pysvn), which
(among other things) can check out (non-recursively) the top-level
directory of a branch and, given a file that resides in a directory
below it, update (non-recursively) all directories in between.
As far as I have tested that, it works fine.

Of course, with the -O option I proposed, It would be up to 800
times faster...


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 11 22:11:59 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.