From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist
Date: Fri, 29 Apr 2016 00:06:00 -0000 [thread overview]
Message-ID: <5722A131.6010001@redhat.com> (raw)
In-Reply-To: <1606116423.20160429020650@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On 04/28/2016 05:06 PM, Andrey Repin wrote:
>> Bottom line, I think the native symlink creation code should be
>> checked and a possibility should be added to create links to
>> non-existent targets, rather than the current behavior of failing.
>
> This is actually an arguable behavior, even in Linux. I can imagine the
> behavior is "undefined" in such a case.
POSIX says a symlink to a missing target is perfectly well-defined (you
can't stat() through it, but you can readlink() it). But Windows native
symlinks can't do that. So the problems you are encountering all stem
from the fact that you are trying to make Windows do something it can't.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-04-28 23:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 22:18 Gene Pavlovsky
2016-04-28 23:48 ` Andrey Repin
2016-04-29 0:06 ` Eric Blake [this message]
2016-04-29 5:23 ` Andrey Repin
2016-04-29 0:09 ` Gene Pavlovsky
2016-04-29 1:46 ` Gene Pavlovsky
2016-04-29 12:03 ` Gene Pavlovsky
2016-04-29 12:15 ` Peter Rosin
2016-04-29 12:20 ` [cygwin] " Jason Pyeron
2016-04-30 12:35 ` Gene Pavlovsky
2016-10-05 3:56 ` Rinrin
2016-10-05 4:31 ` Marco Atzeri
2016-10-06 10:38 ` Gene Pavlovsky
2016-10-07 5:33 ` Rinrin
2016-10-09 19:16 ` Gene Pavlovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5722A131.6010001@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).