I tried again and I put $|=1 before the print , but it is still not working
and I can not see the print "$dest_name\n"; in STDOUT
I modified par.pl as shown below. Please forgive me, Can you tell me the
exact steps to get PAR source (URL) and compile. I usually use to use
ActivePerl's ppm to install package. I am using ActivePerl Build 822 with
latest PAR (0.976) packages in their repository Thanks a lot.
================================
$|=1;
if (defined $ENV{PAR_TEMP}) { # should be set at this point!
foreach my $member ( $zip->members ) {
next if $member->isDirectory;
my $member_name = $member->fileName;
next unless $member_name =~ m{
^
/?shlib/
(?:$Config::Config{version}/)?
(?:$Config::Config{archname}/)?
([^/]+)
$
}x;
my $extract_name = $1;
my $dest_name = File::Spec->catfile($ENV{PAR_TEMP},
$extract_name);
if (! -f $dest_name ) {
print "$dest_name\n";
$member->extractToFileNamed($dest_name);
outs(qq(Extracting "$member_name" to "$dest_name"));
} else {
outs(qq(Skipping "$member_name" since it already exists
at "$dest_name"));
}
}
}
On 1/8/08, Scott Stanton <[EMAIL PROTECTED]> wrote:
>
> I tried the patch and it worked for me, without the -f options since I
> don't have those packages installed. Make sure you are patching the
> par.pl in the source distribution and that you do a clean build and
> install of the PAR::Packer package with the patch applied. An
> incremental build after the change might not be enough.
>
> Also, you may see no debug output due to buffering. Try setting $|=1 at
> the top of the script.
>
> --Scott
>
> -----Original Message-----
> From: Roderich Schupp [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 08, 2008 9:27 AM
> To: Steffen Mueller
> Cc: Henry Wu; Scott Stanton; [email protected]
> Subject: Re: problem with pp
>
> On Jan 8, 2008 4:55 PM, Steffen Mueller <[EMAIL PROTECTED]>
> wrote:
> > Sorry, but I can't test it. It's only going to break on Windows and I
> > currently have no access to that.
>
> I can reproduce Henry's problem here (Active perl 5.8.8 with latest
> PAR::Packer).
> I can also reproduce that the fix doesn't work. I think that it's in the
> wrong place: when running testpp.exe with PAR_DEBUG=1 shouldn't I see
> the
> outs(...) messages in both cases - but there's no debug output at all.
>
> Cheers, Roderich
>
