On 10/2/07, Steve Sisak <sgs@codewell.com> wrote:
> At 8:52 AM -0400 10/2/07, Andy Levy wrote:
> > > Based your response to my question (and similar questions by Mac OS
> >> developers in the past), I can assume your advice to unix users to be
> >> "The only solution at present is the one you've already found: don't
> >> use unix permissions or symlinks." ;-)
> >
> >Subversion does store and version symlinks.
>
> Sorry if I misunderstand -- from the header to asvn:
>
> # Description:
> # Archive SVN (asvn) will allow the recording of file types not
> # normally handled by svn. Currently this includes devices,
> # symlinks and file ownership/permissions.
How old is that? I'm almost certain that SVN supports symlinks today.
> >They get slightly garbled when checked out on Windows (actually
> >changed to text files and aren't usable on that OS). So the advice is
> >"if you have to share your project with Windows users, you have to
> >either not use, or be very careful about how you use, symlinks."
>
> OK, so you hate all non-unix platforms equally. ;-)
No, the issue is that NTFS hasn't supported symlinks *at all* until Vista.
> So it looks like there's a need for a solution for Windows here as
> well -- provide client-side post processing to convert symlinks to
> Windows shortcuts.
Windows shortcuts *are not* symlinks. Not even close. They are not
interchangeable. The fact that SVN can version both makes attempting
to do this (erroneous) "conversion" dangerous and foolish IMO.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 2 16:02:47 2007