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

Re: sparse checkouts and svn:externals

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-10-02 04:06:44 CEST

Jack Repenning <jrepenning@collab.net> writes:
> Is the present behavior of svn:externals under sparse checkouts right?
> What I see (r26847) is that svn:externals directories are only
> created when their parent directory is checked out "--depth
> infinity". It seems to me that these directories-created-by-
> svn:externals are subdirectories, just like the more ordinary ones,
> and should be included in "--depth immediates" (at --depth empty, of
> course, just like the ordinary ones).

I can see arguments both ways for how they should behave at
non-infinity depths, but...

> Further, svn:externals presently breaks stickiness, populating (at
> depth infinity) from any subsequent, depth-less "svn up", even when
> legitimately missing (that is, when the parent checkout was "files"
> or "empty"):
> $ svn co file:///svn/sparse/trunk sparse --depth files
> $ svn stat -v --depth infinity sparse
> 8 8 jrepenning sparse
> 8 8 jrepenning sparse/afile
> $ svn plist -v sparse
> Properties on 'sparse':
> svn:externals : ext-whatever file:///svn/sparse/ext
> $ cd sparse
> $ svn up
> Fetching external item into 'ext-whatever'
> A ext-whatever/afile
> A ext-whatever/sub1
> A ext-whatever/sub1/afile
> A ext-whatever/sub1/sub2
> A ext-whatever/sub1/sub2/sub3
> Updated external to revision 8.
> Updated to revision 8.
> This, of course, is also contrary to the behavior of ordinary
> subdirectories.

...this bit is simply a bug, of course :-). I've filed new issue
http://subversion.tigris.org/issues/show_bug.cgi?id=2954 for it,
assigned it to myself, and growled threateningly at it a bit.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 2 04:06:54 2007

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

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