On Wed, Sep 05, 2012 at 12:52:29AM +0100, Steven Hartland wrote:
Quite an old issue,
Uh yeah. So really no need to resurrect it.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Quite an old issue, its due to the special handling of .exe files if you search
the archives you'll find lots of mentions of it.
Regards
Steve
- Original Message -
From: Aaron Schneider
$ touch myfile myfile.exe
$ tar -cvf mytar.tar myfile.exe myfile
$ tar -xvf
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.
On Fri, Jul 13, 2012 at 09:20:11AM -0700, Andy Hall wrote:
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
On 7/13/12 10:26 AM, Christopher Faylor wrote:
So, everyone, please let this drop unless you have a constructive
suggestion.
Speaking of pragmatism: what about a CYGWIN environment variable to
turn off the behavior? That way, people like the OP could extract
their archives without worry, and it
Greetings, Steven Hartland!
There really is not much point in rehashing this again under a different
subject.
If you or anyone would like to offer patches which change the behavior
emphasis
while keeping everyone happy about .exe handling
/emphasis
please do so.
Isn't the commit which
On 7/12/2012 8:03 AM, Andrey Repin wrote:
Greetings, Steven Hartland!
There really is not much point in rehashing this again under a different
subject.
If you or anyone would like to offer patches which change the behavior
emphasis
while keeping everyone happy about .exe handling
/emphasis
On 7/12/2012 8:03 AM, Andrey Repin wrote:
Greetings, Steven Hartland!
There really is not much point in rehashing this again under a
different
subject.
If you or anyone would like to offer patches which change the behavior
emphasis
while keeping everyone happy about .exe handling
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
On Thu, Jul 12, 2012 at 06:41:47PM +0200, Otto Meta wrote:
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
Greetings, Andy Hall!
At the risk of adding more fuel to the fire, let me add my 2 cents worth to
this.
1. As a long time and frequent user of tar and rsync to transfer files and
directories between Windows and various UNIX flavors, I have been astonished
(and severely burned) by the fact
On 7/11/2012 10:50 PM, Aaron Schneider wrote:
$ touch myfile myfile.exe
$ tar -cvf mytar.tar myfile.exe myfile
$ tar -xvf mytar.tar
Only myfile will be written to the filesystem
Aaron,
you are starting to bore.
it seems that you ignored every info
- Original Message -
From: Aaron Schneider
$ touch myfile myfile.exe
$ tar -cvf mytar.tar myfile.exe myfile
$ tar -xvf mytar.tar
Only myfile will be written to the filesystem
Yep, apparently its by design :(
It causes us pain regularly so we would like this fairly
recent change
On Thu, Jul 12, 2012 at 01:39:41AM +0100, Steven Hartland wrote:
From: Aaron Schneider
$ touch myfile myfile.exe
$ tar -cvf mytar.tar myfile.exe myfile
$ tar -xvf mytar.tar
Only myfile will be written to the filesystem
Yep, apparently its by design :(
It causes us pain regularly so we
- Original Message -
From: Christopher Faylor
On Thu, Jul 12, 2012 at 01:39:41AM +0100, Steven Hartland wrote:
From: Aaron Schneider
$ touch myfile myfile.exe
$ tar -cvf mytar.tar myfile.exe myfile
$ tar -xvf mytar.tar
Only myfile will be written to the filesystem
Yep,
15 matches
Mail list logo