Skip Menu |

This queue is for tickets about the PAR CPAN distribution.

Report information
The Basics
Id: 6613
Status: resolved
Priority: 0/
Queue: PAR

People
Owner: Nobody in particular
Requestors: rcaputo [...] pobox.com
Cc:
AdminCc:

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



Date: Sun, 13 Jun 2004 12:37:54 -0400
From: Rocco Caputo <rcaputo [...] pobox.com>
To: bug-PAR [...] rt.cpan.org
Subject: PAR executables see PERL5LIB/PERLLIB environment
I'm not sure if I'm reporting a bug or a feature. On development machines, programs that load modules at runtime will not fail if they aren't given the proper -M options. The PAR executables will fetch necessary modules from @INC if they aren't available in its cache. Of course they'll fail after being deployed to systems that don't have all the necessary modules (or Perl at all). This is an excellent argument for using staging/testing servers. As a workaround, PAR could force the executable to fail in development as well as deployment. It could replace @INC entirely, blinding itself to the installed Perl and its libraries. -- Rocco Caputo - http://poe.perl.org/
From: bovine
[rcaputo@pobox.com - Sun Jun 13 13:49:28 2004]: Show quoted text
> As a workaround, PAR could force the executable to fail in development > as well as deployment. It could replace @INC entirely, blinding > itself to the installed Perl and its libraries. >
I would like to see PAR'ed executables completely ignore any installed Perl environment and run entirely self-contained. We are seeing DLL library conflicts resulting from users having a different version of Perl already installed, and its modules are being found first even when all of the necessary modules were included in the PAR archive.
Date: Wed, 21 Jul 2004 08:31:49 -0700
From: Autrijus Tang <autrijus [...] gmail.com>
To: bug-par [...] rt.cpan.org
Subject: Re: [cpan #6613] PAR executables see PERL5LIB/PERLLIB environment
RT-Send-Cc:
On Tue, 20 Jul 2004 14:38:21 -0400 (EDT), Guest via RT <bug-par@rt.cpan.org> wrote: Show quoted text
> I would like to see PAR'ed executables completely ignore any installed > Perl environment and run entirely self-contained. We are seeing DLL > library conflicts resulting from users having a different version of > Perl already installed, and its modules are being found first even when > all of the necessary modules were included in the PAR archive.
Really? That was specifically fixed with PAR 0.81,and should not manifest itself again with the newest version, 0.85. Can you duplicate this problem with PAR 0.85? Thanks, /Autrijus/