One of my users has a relative externals definition that points to a
directory like this:
../../../libraries/app/release
When TSVN checks out this project, this external is properly checked out
along with it. However, when the Subversion CLI checks it out, it
chokes on that with the error "svn: Invalid svn:externals property on
'External': target '../../../libraries/app/release' is an absolute path
or
involves '..'"
Since that appears to be by design, according to
http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.advanced.externals,
and at least one version of the Tortoise docs use something like that as
an explicit example,
http://tortoisesvn.net/docs/release/TortoiseSVN_en/help-onepage.html#tsvn-dug-import-4,
it seems that TSVN is doing something behind the scenes to make it work
properly, or at least appear to. My question is, what precisely is TSVN
doing, and will it work properly if we copy that entire tree, including
everything referenced by the external, to a branch?
Since our build servers use the CLI, is there a way to see what Tortoise
is doing, so we can set the actual external definition to that, in order
to make the CLI work as well?
Thanks,
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-09-09 17:36:33 CEST