X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,TW_YG X-Spam-Check-By: sourceware.org Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1244.3) Subject: Re: tar deletes .exe files on extraction (again) From: Steve Atkins In-Reply-To: Date: Fri, 23 Sep 2011 09:14:51 -0700 Message-Id: References: <4E7BE736 DOT 1060008 AT cygwin DOT com> <4E7C9DF7 DOT 2090200 AT cs DOT utoronto DOT ca> To: cygwin AT cygwin DOT com X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p8NGFLUO016017 On Sep 23, 2011, at 8:34 AM, Andrew DeFaria wrote: > On 09/23/11 07:55, Ryan Johnson wrote: >> >> Wild speculation here... >> >> A quick test shows that ./a indeed works fine inside cygwin whether the '.exe' is present or not, though it would be a little challenging invoke such binaries directly from Windows. >> >> So... how hard would it be to provide "CYGWIN=(no)disabletransparent_exe"?*** There could a very simple utility, similar to rebaseall, which strips the .exe extension from cygwin executables (identifiable from cygcheck or their presence in standard paths), and which accepts additional paths to clean up. People needing the functionality would be responsible run the utility properly (after installing new packages, don't mess with Windows paths, etc.). >> >> That would require no changes to any package to give the desired behavior, and as packages change they would just fit right in (no .exe in the package ==> no fuss). >> >> Of course, SHTDI... >> >> Ryan >> >> *** The old, removed "transparent_exe" has the wrong boolean sense to work the correct way by default >> > What do you do about say, Foo.c and foo.c? The same as you do now on cygwin and on other case-preserving but case-insensitive filesystems - treat them as identical. That's still a little annoying, but not uncommon on unix-ish environments (OS X as one common example) so people already are aware of it and work around it. Cheers, Steve -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple