DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1B1F938460B4
Message-ID: <970d3bc2-497e-4f10-a3e0-8b9701d8601b@dronecode.org.uk>
Date: Thu, 25 Apr 2024 14:15:02 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: native symlinks and non-existent targets
To: clayne@anodized.com
References: <ZimDqKx1R13FdV2q@mercury.signalpunk.com>
 <ZimJchxllNm8P96S@mercury.signalpunk.com>
Content-Language: en-US
Cc: cygwin@cygwin.com
In-Reply-To: <ZimJchxllNm8P96S@mercury.signalpunk.com>
Precedence: list
From: Jon Turney via Cygwin <cygwin@cygwin.com>
Reply-To: Jon Turney <jon.turney@dronecode.org.uk>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On 24/04/2024 23:36, Christopher Layne via Cygwin wrote:
> On Wed, Apr 24, 2024 at 10:11:52PM +0000, Christopher Layne via Cygwin wrote:
>> Based on past threads I've read I believe the issue is actually with
>> windows not allowing a symlink to be created with a non-existent target,
>> but I do know windows does not care if you break a link after the fact.
> 
> Actually, after referring to some microsoft documentation, is this even
> true?

No.

However, native symlinks do record the type (file or directory) of the 
destination, and (absent special knowledge) this cannot be determined if 
the destination doesn't exist (yet).

If I recall correctly, Cygwin doesn't care if the type recorded in the 
symlink is incorrect, but some parts of Windows do...

> If it isn't true then this seems trivial to fix.

This assertion is trivially disproven by the lack of a patch attached. :)


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple