You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Fogel <kf...@newton.ch.collab.net> on 2002/11/19 18:47:27 UTC
Re: svn and symlinks?
pll@lanminds.com writes:
> How does svn deal with symlinks? Er, rather, will they be a problem?
It doesn't handle them at all right now, and probably won't before
1.0. If you try to import them or add them to a working copy,
something will go wrong :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn and symlinks?
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Paul Lussier <pl...@lanminds.com> writes:
> How does CVS handle this, or is this also a place where CVS breaks
> down?
I think CVS doesn't handle symlinks either.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn and symlinks?
Posted by Paul Lussier <pl...@lanminds.com>.
In a message dated: 19 Nov 2002 13:30:55 CST
Karl Fogel said:
>Since we don't yet support them, we would better return an
>SVN_ERR_UNSUPPORTED_FEATURE error right now, instead of silently
>mishandling them. Can you file an issue with your recipe? This
>shouldn't be too hard to patch.
Sure, I can do that.
>> I'm curious if there are plans to better handle symlinks in the
>> future. And if so, how would that work in a cross-platform
>> environment, e.g. a windows client checking out a repo created from
>> on a UNIX-based platform where symlinks were used?
>
>There is an intention, but not yet a plan. The questions you ask
>above are exactly what we'll need to figure out; but we've deferred
>the discussion until we're actually implementing the feature.k
Okay, fair enough. Not a big deal right now.
How does CVS handle this, or is this also a place where CVS breaks
down?
--
Seeya,
Paul
--
It may look like I'm just sitting here doing nothing,
but I'm really actively waiting for all my problems to go away.
If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn and symlinks?
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Paul Lussier <pl...@lanminds.com> writes:
> Hmmm, I just tried it out before I read this response.
> Interestingly, I created a couple of symlinks within a wc,
> then committed, and everything went fine. Now, though, when I check
> out a new wc, I get 2 copies of the file, not one copy and a symlink
> to that copy.
Since we don't yet support them, we would better return an
SVN_ERR_UNSUPPORTED_FEATURE error right now, instead of silently
mishandling them. Can you file an issue with your recipe? This
shouldn't be too hard to patch.
> I'm curious if there are plans to better handle symlinks in the
> future. And if so, how would that work in a cross-platform
> environment, e.g. a windows client checking out a repo created from
> on a UNIX-based platform where symlinks were used?
There is an intention, but not yet a plan. The questions you ask
above are exactly what we'll need to figure out; but we've deferred
the discussion until we're actually implementing the feature.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn and symlinks?
Posted by Paul Lussier <pl...@lanminds.com>.
In a message dated: 19 Nov 2002 12:47:27 CST
Karl Fogel said:
>pll@lanminds.com writes:
>> How does svn deal with symlinks? Er, rather, will they be a problem?
>
>It doesn't handle them at all right now, and probably won't before
>1.0. If you try to import them or add them to a working copy,
>something will go wrong :-).
Hmmm, I just tried it out before I read this response.
Interestingly, I created a couple of symlinks within a wc,
then committed, and everything went fine. Now, though, when I check
out a new wc, I get 2 copies of the file, not one copy and a symlink
to that copy.
I'm curious if there are plans to better handle symlinks in the
future. And if so, how would that work in a cross-platform
environment, e.g. a windows client checking out a repo created from
on a UNIX-based platform where symlinks were used?
Thanks,
--
Seeya,
Paul
--
It may look like I'm just sitting here doing nothing,
but I'm really actively waiting for all my problems to go away.
If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org