This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: native symlink support should fallback to default format if target missing
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Mon, 13 May 2013 17:00:46 +0200
- Subject: Re: native symlink support should fallback to default format if target missing
- References: <20130424181412 dot GB26397 at calimero dot vinschen dot de> <3B3671F5-EBFE-480B-B592-90BA2270BDA6 at mac dot com> <42E7B9C6-1A6A-43D7-84B3-AEDD25EF4507 at mac dot com> <517F061D dot 5080201 at cygwin dot com> <671E245A-BDCD-4F46-90B7-9E73301126C1 at mac dot com> <20130430002548 dot GA7635 at ednor dot casa dot cgf dot cx> <9FCBD602-2D9C-4069-AA5F-682C32DE6D32 at mac dot com> <517F13D1 dot 8040105 at cwilson dot fastmail dot fm> <B225793A-09C6-4E2C-B257-5A7FAF7E990E at mac dot com> <56151889-406D-4648-BFC9-BEE3AE70D56E at mac dot com>
- Reply-to: cygwin-developers at cygwin dot com
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
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat