From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <corinna@sourceware.org>
Received: by sourceware.org (Postfix, from userid 2155)
	id 657D83858C42; Mon,  8 Jan 2024 18:11:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 657D83858C42
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1704737511;
	bh=7ZzEx6nIe4Ovtfpz+eH/qYHKETnKtExlPBYhd62X1Dc=;
	h=Date:From:To:Subject:Reply-To:References:In-Reply-To:From;
	b=VJnp1sPrGJz9h71eXFY9pxKtQLblcq9PINbVK2BCB+Ppkgfs5o7W8FzIDFS/reBJM
	 xojMRus7EImIJLNxIJeMv3X8bzr0i8HEcwZHUHLWDATnrbXxARcBotymdR9JyTJ2dZ
	 uoY0AfqKbQfli0acpKZk3gb6CSyuBwpkbEVPCZZk=
Received: by calimero.vinschen.de (Postfix, from userid 500)
	id 97C71A806FF; Mon,  8 Jan 2024 19:11:49 +0100 (CET)
Date: Mon, 8 Jan 2024 19:11:49 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin generates syscalls for *.lnk files on filesystems with
 native symlink support?
Message-ID: <ZZw65R578QtNO_4E@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CALXu0UfRxk5G=3OjbwoNFW7xSj1rHTNw5giS6YZb9p1gF5ceTA@mail.gmail.com>
 <ZPHDrz7VedOBROtT@calimero.vinschen.de>
 <CALXu0Ue9SyJod+0k24pQzs3KPg1RPquRfhN3tw3GYG-qMt_+DQ@mail.gmail.com>
 <ZZv_K1NyxE-btqQt@calimero.vinschen.de>
 <266017637.5531727.1704733902023@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <266017637.5531727.1704733902023@mail.yahoo.com>
List-Id: <cygwin.cygwin.com>

On Jan  8 17:11, matthew patton via Cygwin wrote:
> > For instance: Getting rid of .lnk files isn't easy with backward compatibility in mind.
> screw backward compatability! :)Why carry around bandaids on bandaids
> for an OS that is 10 years out of support?

We're using .lnk files for FIFOs. That's the compat concern, not some OS
from the past.

> Obviously not ripe for 3.6 or maybe even 3.7, but at some point we
> should just put a stick in the sand and say this .lnk crap is dead and
> you have to either compile it back in with an IFDEF or a CYGWIN var.

No ifdefs, and a Cygwin var setting unfortunately exists.

> And while we're at it use OS-native links instead of Junctions. I'm
> not sure how that came about but Junctions are unhelpful.

Cygwin does not create symlinks as junctions.  No idea where you got
that idea.


Corinna