Finley, Stephen wrote:
>I set the properties on a directory to be an external to a specific
>revision. If I do an update at the top level I get the correct code, but
>if I do an update on the external directory I get the latest code for
>those files not the revision. I believe this is an error in subversions
>handling of externals.
>[...]
>Myproject has property set to use external revision 5 of
>myproject2/common-files in directory common-files
That's not a bug, it's a feature 8-)
This behaviour is by design. the svn:externals property is only
relevant to the wc it is set on (myproject2), and only in case of svn
co/up.
The subfolder (common-files) on the other hand is a wc of its on,
that knows nothing about the way it was created.
So an svn co/up on myproject2 knows to pull in revision 5 of
common-files, but an update on common-files itself will get you HEAD.
As you want it to stay on a specific revision, the appropriate command
would be "svn up -r 5 ...".
But as common-files is already at revision 5 that command would do
nothing.
HTH
Lorenz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 6 08:58:19 2007