Hi Neels
Thanks very much for your answer. It clarified svn's behaviour with externals for me.
With best regards
David
________________________________________
From: neels [neeels_at_gmail.com]
Sent: 12 March 2010 14:08
To: David Aldrich
Cc: users_at_subversion.apache.org
Subject: Re: Unexpected Externals behaviour in working copy
On 12 March 2010 11:28, David Aldrich <David.Aldrich_at_eu.nec.com> wrote:
> Hi
>
> I haven't had a reply to this question of mine yet. So I would like to rephrase it:
>
> Is it true that if I delete an external relating to a folder or file then svn will not automatically delete that folder/file from my local working copy?
Hi David,
when I analysed externals in 1.6 about a year ago, that is what I
found. I consider it a bug.
It's like this:
Dir externals are not removed from your WC, but they are "forgotten"
alright. If you remove the external prop, remove the external folder
and svn up, it is still gone.
File externals are not even capable of being forgotten! If you remove
the prop, remove the file, and then update, the damn thing *comes
back*! That's a stupid bug, no-one has gotten around to fix it yet.
You need a new checkout of the parent folder.
I attached a script that illustrates externals behaviour. I tested with 1.6.x.
~Neels
>
> This seems to be related to Subversion issue #3351 (although that issue only relates to file externals, not folder externals).
>
> It is seems that a fresh check out is required. Or is it ok to delete the 'external' folder/file in my wc using an operating system delete operation?
>
> Best regards
>
> David
>
> ________________________________________
> From: David Aldrich [David.Aldrich_at_eu.nec.com]
> Sent: 11 March 2010 16:11
> To: users_at_subversion.apache.org
> Subject: Unexpected Externals behaviour in working copy
>
> Hi
>
> I have a question about externals. I tried the following scenario in my working copy:
>
> 1) Add an external definition to directory A, specifying subdirectory B
> 2) Commit directory A
> 3) Update directory A
>
> I then see A/B populated
>
> Then:
>
> 4) Edit external definition to directory A, specifying subdirectory C
> 5) Commit directory A
> 6) Update directory A
>
> I then see A/C populated, but directory A/B remains in the wc.
>
> If I checkout a new working copy, it shows A/C but not A/B, as expected.
>
> So, in short, changing an external definition on a directory seems not to remove the previous external content from the committer's working copy.
>
> I hope this makes sense. Please will someone explain?
>
> Best regards
>
> David
>
>
>
> Click https://www.mailcontrol.com/sr/nypLE7lZxS7TndxI!oX7UvIItv2OGGpTAw!IKZCqldsHAq!cPr+aidCSu5mXugUL!MaMXUtHUxa1yubdBaCdqw== to report this email as spam.
Received on 2010-03-12 15:25:02 CET