If you chose to solve your problem with symlinks, be aware that if some of
your users wants to check out the repo on a network file system (nfs or
samba share) the checkout can fail under some circumstances, because these
file systems does not allow to create a symlink without having a valid
target for the symlink. This happens if for example the symlink and the
target resides in the same repo and the symlink gets checked out before the
target.
Currently I don't know any other work around that checking out the repo on a
local drive and move it afterwards to the network share. If there are others
out there with a better solution I would be glad to get a hint...
Andreas
>On 7/21/07, Morten <lists@kikobu.com> wrote:
>>
>> Hi. I'm aware that svn:externals only works for directories. What I'm
>> trying to accomplish, is a setup such that:
>>
>> project_1/foo -> svn://project_2/foo (svn:externals)
>> project_1/bar/baz.ext -> svn://project_2/bif/baz.ext (??)
>>
>> Is this possible in any way?
>
>svn:externals only operates with directories. If all of your clients are
using environments in which UNIX-style
>symlinks are supported, Subversion's ability to version symlinks may help
you achieve what you're looking for.
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.12/910 - Release Date: 21.07.2007
15:52
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 22 19:39:40 2007