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

RE: Re: Updating a folder containing external files results in deleting the files

From: Daniel Morgan <m-daniel_at_apn.alpine.co.jp>
Date: Fri, 18 May 2012 01:00:02 -0700 (PDT)

> I saw similar issues discussed on users_at_subversion several times
> during last months, and it is not a bug. It is a feature that worked
> by mistake. By "the feature" I mean including additional directories
> into the filename of an external.
> I cannot say authoritatively about folder externals using this feature
> (you'd better look at users(at)subversion.apache.org list and maybe
> recent updates to the book), but in your case of file externals it is
> little wonder that it does not work.
> File externals are known to be an odd beast since their birth. They
> internally are implemented as a switched file. In your case "FD2/FD3"
> does not belong to a working copy so it cannot contain switched files.
> I do not know how it ever worked in svn 1.6.

Thank you for your response.
Let me edit the example repository to clear any confusions.

| +---branches
| +---tags
| \---trunk
| \---FD1
| \---FD2
| \---FD3
| test.txt

svn:externals is set on PRJ_B\trunk\FD4 as:
^/PRJ_A/trunk/FD1/FD​2/FD3/test.txt FD5/FD6/test.txt

Folder FD5 and FD6 exist and belong to trunk of PRJ_B.
I assume this means that FD5/FD6 does belong to the working copy.

On the other hand, if I'm understanding the details in your response correctly, I am not using file externals the right way.
If adding directory paths to a file external is a problem itself, the correct way to add the external would be to set it on PRJ_B\trunk\FD4\FD5\FD6 as:
^/PRJ_A/trunk/FD1/FD​2/FD3/test.txt test.txt

Is this what you were trying to point out?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-05-18 10:00:08 CEST

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

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