X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0	tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_YG
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew DOT DeFaria AT tellabs DOT com>
Subject: Re: tar deletes .exe files on extraction (again)
Date: Fri, 23 Sep 2011 10:41:08 -0700
Lines: 36
Message-ID: <j5igbl$usl$1@dough.gmane.org>
References: <DDC20689-EA66-49D5-A120-6AC40BE05900 AT blighty DOT com> <4E7BE736 DOT 1060008 AT cygwin DOT com> <4E7C9DF7 DOT 2090200 AT cs DOT utoronto DOT ca> <j5i8ts$994$1 AT dough DOT gmane DOT org> <B537E8D3-F689-469E-AC87-FBC9FE442281 AT blighty DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
In-Reply-To: <B537E8D3-F689-469E-AC87-FBC9FE442281@blighty.com>
X-Stationery: 0.7.5
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 9/23/2011 9:14 AM, Steve Atkins wrote:
> 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
My point, obviously missed, was that I thought that the issue here was 
that if you untar a tar which contains say a.exe and a as two different 
files the later one will overwrite the former due to the way that Cygwin 
treats files that end in .exe. Wouldn't you have a similar problem if 
you had Foo.c and foo.c in the tar image? (Note I didn't know about that 
registry setting which is interesting and which I'd venture to guess 
nobody runs with).

If people "work around" the Foo.c/foo.c issue, presumably by renaming 
one of the files, couldn't they likewise "work around" the a.exe/a issue?
-- 
Andrew DeFaria <http://defaria.com>
Reality is a crutch for people who can't handle drugs.


--
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