native symlink support should fallback to default format if target missing
Corinna Vinschen
corinna-cygwin@cygwin.com
Mon May 13 15:40:00 GMT 2013
On May 13 11:25, Jeffrey Altman wrote:
> On 5/13/2013 11:00 AM, Corinna Vinschen wrote:
> > On May 3 14:53, James Gregurich wrote:
> >> The guy I have testing the native symlink support in the new cygwin is
> >> reporting to me that if the target of the link does not exist, the
> >> mechanism is creating a file reparse point. This is not desirable
> >> behavior. When the target comes into existence, if it is a folder,
> >> then the native symlink is invalid. What the mechanism should do is
> >> fall back to the native symlink format if the target doesn't exist.
> >> That way, the link is never invalid. Since it is a default format
> >> symlink, then my test for the need to replace the link by checking if
> >> it is not a reparse point will work. Otherwise, I would have to take
> >> into consideration that the reparse point may exist but be invalid.
> >
> > Makes sense. I'll fix that shortly.
>
> Corinna,
>
> Don't worry about falling back for AFS. The correct thing will happen
> there because AFS does not save the target type information as part of
> the backend link information.
Thanks for the reminder. I'll keep that in mind for the patch.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
More information about the Cygwin-developers
mailing list