Skip Menu |

This queue is for tickets about the Archive-Extract CPAN distribution.

Report information
The Basics
Id: 113487
Status: resolved
Worked: 5 hours (300 min)
Priority: 0/
Queue: Archive-Extract

People
Owner: Nobody in particular
Requestors: scott [...] tropare.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 0.80



Subject: Issue with ON_LINUX unzip check, also Perl EPIC validation and Archive::Extract
Date: Thu, 31 Mar 2016 11:47:21 -0700
To: bug-Archive-Extract [...] rt.cpan.org
From: Scott Deardorff <scott [...] tropare.com>

Message body is not shown because it is too large.

Subject: [rt.cpan.org #113487]
Date: Fri, 1 Apr 2016 16:10:44 -0700
To: bug-Archive-Extract [...] rt.cpan.org
From: Scott Deardorff <scott [...] tropare.com>
I wanted to update this with some additional information. I got some help from the Perl EPIC guys and the following appears to be the issue: From Jan Ploski at EPIC. To reproduce them from shell (without EPIC's involvement), you can use the following invocation "cat yourcode.pl | perl -c" instead of just "perl -c yourcode.pl". This simulates how EPIC passes the source code to the compiler. The reason for those errors seems to be that IPC::Cmd does funny things to STDIN (in the dup_fds and reopen_fds functions - if you comment them out, the syntax errors disappear). Anyway, it's not a good practice to run external programs as a side effect of mere compilation, so that part might need to be fixed by Archive::Extract. BTW, in my environment full path of the program (/usr/bin/unzip) is passed to the "run" function, unlike what you mentioned earlier. Thanks for your help on this.
On Fri Apr 01 19:10:58 2016, scott@tropare.com wrote: Show quoted text
> > Anyway, it's not a good practice to run external programs as a side > effect of mere compilation, so that part might need to be fixed by > Archive::Extract. BTW, in my environment full path of the program > (/usr/bin/unzip) is passed to the "run" function, unlike what you > mentioned earlier. > > Thanks for your help on this.
Hi, This shouldn't be an issue since version 0.80 of Archive::Extract as suitable binaries are now determined heuristically rather than attempting to execute the binaries.