X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.0 required=5.0	tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
From: "Andy Hall" <fixpertise-consulting AT comcast DOT net>
To: <cygwin AT cygwin DOT com>
References: <BLU152-W148807FCA9B75410CB8F1FCED10 AT phx DOT gbl> <92B65842B4224F3FA65CE40F3608F7DF AT multiplay DOT co DOT uk> <20120712010353 DOT GB14112 AT ednor DOT casa DOT cgf DOT cx> <447894CEE2E7427F8E0AFC5A206BAD92 AT multiplay DOT co DOT uk> <981681190 DOT 20120712160313 AT mtu-net DOT ru> <4FFED62A DOT 7060106 AT cygwin DOT com> <EEF3431C30314B69B826B954F2D49B64 AT ahallpc> <4FFEFE4B DOT 5060107 AT sister-shadow DOT de>
Subject: RE: tar won't extract all files when a file with exe extension precedes the same without extension inside the archive
Date: Fri, 13 Jul 2012 09:20:11 -0700
Message-ID: <CBCD3DC43BC94D5E9634AE133FA7E8A5@ahallpc>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <4FFEFE4B.5060107@sister-shadow.de>
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

> 
> > 2.  Since this is a "Windows thing", is there some reason why the
> execution
> > of "file" or "file.exe" isn't handled as a special case in the exec call
> > (and all its flavors) and no place else?
> 
> make, for example? If you have a rule that creates "foo" from foo.c,
> gcc will actually create "foo.exe". The next time you run make, it
> won't see "foo" and recreate "foo.exe", even if "foo.exe" is still
> up to date.
> 
> With the special handling of .exe, when make checks for "foo", cygwin
> checks "foo" first, doesn't find anything, and then checks "foo.exe",
> returning its result to make and make is happy.
> 
> Anothen example: A script tries to execute "foo" from . , cygwin
> executes "foo.exe" instead and the script thinks "foo" exists,
> but a subsequent "touch foo" (or "rm foo" or whatever) fails, which
> is massively inconsistent.
> 
> I consider the current handling of .exe files quite consistent.
> 
> Or, in other words, when forced to choose between the two pains,
> I'd rather endure this.
> 
> Otto
> 
Well, this seems to be something that has to be addressed specifically in
make and gcc (and other similar places).  If make has a rule to create "foo"
from foo.c, then that is what it should do!  Dennis Ritchie would turn over
in his grave is he heard that commands like tar, rsync, zip, ... were not
idempotent WRT at least filenames and contents, let alone permissions.  

Andy



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