X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE4963858282 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1704737568; bh=Z37m/CBWxFJXqAkfuFhDMNZBziDQKwqHZwvJgao3V7s=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=RGzmgEdF+Do8EvPvcZyhGhinxezKWvRMgl85b8Ijn/FZTcje38sdGnD2XWyjIRSgq OsmDYF1bRPv6xJKDcv1fooqyKQeR7fn1XHnb9bXtLmm2Iv89ME3jMYaqjaJ+t1tcgR oO8OBQAWdcaR35OWY/IY/VoEmFrIQ2ddiPui2niI= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 657D83858C42 Date: Mon, 8 Jan 2024 19:11:49 +0100 To: cygwin AT cygwin DOT com Subject: Re: Cygwin generates syscalls for *.lnk files on filesystems with native symlink support? Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: <266017637 DOT 5531727 DOT 1704733902023 AT mail DOT yahoo DOT com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <266017637.5531727.1704733902023@mail.yahoo.com> X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="utf-8" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 408ICpir024268 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 -- 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