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

Re: SVN does not allow checking out parent dir if its child dir has been checked out

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-19 17:05:50 CEST

On Aug 19, 2006, at 15:08, Chen(陈? Jun(军? wrote:

> I'm using Subversion 1.3.0 (r17949) on Windows 2000 SP4.
> Assume that I have a repository at h:/temp/SvnReps/ChjTrivials ,
> and the C:/ChjTrivials directory does not exist yet.
> Now, I issue the command: <pre>
> C:\>svn co file:///h:/temp/SvnReps/ChjTrivials/trunk/ichsize
> ChjTrivials/ichsize </pre>
> SVN outputs:
> <pre>
> A ChjTrivials\ichsize\ichsize.cpp A ChjTrivials\ichsize
> \ichsize.dsp Checked out revision 4. </pre>
> The checkout is success, and I have what I want in C:/ChjTrivials/
> ichisze
> But, when I further issue the following command:
> <pre>
> C:\>svn co file:///h:/temp/SvnReps/ChjTrivials/trunk ChjTrivials </
> pre>
> SVN outputs: <pre>
> A ChjTrivials\ComHwCtrl A ChjTrivials\ComHwCtrl\ComHwCtrl.cpp
> A ChjTrivials\ComHwCtrl\ComHwCtrl.dsp svn: Failed to add
> directory 'ChjTrivials\ichsize': object of the same name already
> exists </pre>
> Why!!! For the second command, I just want to checkout the parent
> directory of what the first command had checked out, and it could
> not cause any local copy conflict if the second checkout is
> allowed. Why SVN prohibit that?
> Why this make me mad? I'm developing a GNUmake-featured make system
> that can automatically checkout the required source files(.cpp, .h
> etc) as instructed in my makefiles, and those makefiles are often
> written to checkout only part of a CVS or SVN repository(that part
> is enough for the current makefile to build a project). Back to the
> time I used CVS, checking out a child dir then its parent dir is
> not a problem, but when I upgrade my make system to support
> checkout from SVN these days, I found this anonying SVN behavior.
> Do you kind guys have the same experience as I and any solution to
> this?
> BTW: SVN 1.3.2 (r19776) exhibits the same behavior.

I can't answer your question about why Subversion behaves that way,
but I can confirm that Subversion does behave that way.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 19 17:07:19 2006

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.