This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
native symlink support should fallback to default format if target missing
- From: James Gregurich <bayoubengal at mac dot com>
- To: "cygwin-developers at cygwin dot com" <cygwin-developers at cygwin dot com>
- Date: Fri, 03 May 2013 14:53:43 -0700
- Subject: native symlink support should fallback to default format if target missing
- References: <20130403152907 dot GD2468 at calimero dot vinschen dot de> <20130424103450 dot GM26397 at calimero dot vinschen dot de> <5177CABF dot 8040406 at openafs dot org> <20130424125043 dot GA18673 at calimero dot vinschen dot de> <51781CA4 dot 3040103 at openafs dot org> <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>
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.
-James