--- Rafael Garcia-Suarez
<raphel.garcia-suarez@hexaflux.com> wrote:
> As there was some discussion on the possibility of
> storing symlinks into a
> repos, I'd like to suggest something :
>
> symlinks (or hard links, for that matter) are
> basically directory entries
> that point to the same file. Instead of implementing
> Unix symlinks in the
> repository (with all the portability problems), it
> could be useful to have
> a 'svn ln' command, similar to 'svn cp', but that
> doesn't create a new
> branch.
>
> In other words, if you do
> $ svn ln foo bar
> then it creates the resource '/path/bar' in the
> repository, as
> a copy of '/path/foo', but in a way that '/path/bar'
> is always
> updated when '/path/foo' is changed (and
> vice-versa). (For any
> revision N > rev number where bar is created, foo@N
> and bar@N
> are the same.)
>
> When convenient or possible, bar could be created as
> a symlink
> to foo in a working copy, but I don't see a high
> need for this.
I think creating "svn ln" would also be a convenient
way to create tags since a hard link to a particular
revision should automatically be read-only.
MTC,
Noel
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 14 14:12:46 2002