[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: how to make svn _follow_ symbolic links?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Mon, 20 Jul 2009 19:12:00 -0500

Misha Aizatulin wrote:
> All I want is to be able to use a single file from my hard drive in
> several working copies, that's all! At the moment I can do it with
> hardlinks, but they have their limitations, including that they don't
> work for folders.
>
> Would it be possible to implement symbolic link following in svn?
> Shall I post a feature request/bug report? After all that is the
> behaviour of almost all unix programs - they treat the links
> transparently, unless there is a reason to do otherwise. That is where
> the power of symbolic links comes from.
>
> There has been a suggestion to use a script that would copy files and
> then call svn. This is in fact what I have been doing so far, but I hope
> you would agree that this should not be necessary.
Normally you expect version control systems to be able to be able to
reproduce what you committed. If you commit a symlink you should expect
to get a symlink back in a checkout, shouldn't you? When you describe
the behavior of "almost all unix programs" you are conveniently ignoring
the programs intended to do backup/restore or literal copies (tar, cpio,
dump, etc.) which would be the the obvious counterpart for the expected
action. But, why don't you include the 'real' copy in one of the
places you want it, and after committing it, reference the directory
holding it as an external in all those other places you want the same
things to appear?

-- 
  Les Mikesell
   lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2372773
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-21 02:13:07 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.