Re: Unexpected Externals behaviour in working copy
From: Ryan Schmidt <subversion-2010a_at_ryandesign.com>
Date: Fri, 12 Mar 2010 15:57:56 -0600
On Mar 12, 2010, at 15:47, Les Mikesell wrote:
> On 3/12/2010 3:14 PM, Ryan Schmidt wrote:
Off the top of my head, Subversion could notice when you commit a change in the svn:externals property. If the svn:externals property used to pull an external into the directory foo, and you change the property so this no longer happens (including deleting the property), Subversion could check if the directory foo exists, and if so, if it is a working copy of the URL the external definition used to point to. If so, it could do what it does any other time it removes a directory: remove the files if they're not modified, keep them if they are (or are unversioned), delete empty directories.
That would be for the user doing the commit that changes or removes the external. For users updating, Subversion could notice the change in svn:externals on update, and act accordingly.
This is an archived mail posted to the Subversion Users mailing list.