Re: Problems with externals

Hello!

Finley, Stephen schrieb:
> If I do any update on the myproject directory it would get the correct
> version of the files, but if I went and did an update on the
> common-files directory it would update to the latest version of these
> files in /myprojects/common-files not version 5.

Like some other people mentioned here, this is a feature and not a bug.
I have to admit that it can cause lots of problems because the
svn:externals are not really transparent.

But I think that referring to a certain revision in an external is also
very dangerous; instead of using r5 of myproject2/common-files you
should instead first create a tag or release like

svn cp -r5 myproject2/trunk/common-files \
   myproject2/releases/myrelase_123/common-files

and afterwards use the HEAD revision of
myproject2/releases/myrelase_123/common-files for your svn:external
reference.

You have to keep in mind that after restructuring a repository the
revision numbers can have changed, so external references could point
to the wrongs revisions without causing an error message. If after
restructuring a repository a path becomes invalid you would at least
get a proper error.

With best regards
Andreas Schweigstill

-- 
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstraße 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org