Cygwin takes a nice approach to symlinks on windows. If you create a
symlink from within cygwin, it creates a .lnk file - i.e. a windows
"shortcut". Cygwin handles such files specially, treating them as
symlinks from a shell point of view, and programs compiled with cygwin
are also fine. The windows shell is also quite happy with the results -
double-clicking does exactly what you expect.
In a way, shortcuts are not so very different from symlinks. They are
just interpreted at a higher level: the shell rather than the operating
system. As I understand it, neither is as low-level as a hardlink, which
is understood by the filesystem and is transparent to higher layers of
the OS.
Of course, none of the above addresses the problem of how this might be
implemented in subversion...
---Tom Sillence
John Peacock wrote:
> Brian Mathis wrote:
>
>> Windows NTFS does support *hard links*, which give almost identical
>> functionality as symlinks (and exactly identical functionality to unix
>> hard links).
>
>
> And the same limitation as hard links (i.e. must be on the same NTFS
> filesystem). They are also somewhat confusing in that the file
> properties (size, etc) don't change in the hardlink if the original file
> was used to make the change.
>
> John
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 6 17:02:28 2004