Barrie Slaymaker wrote:
On Wed, Jan 21, 2004 at 06:01:08PM -0700, Mike Schroeder wrote:Yep - I used -M LWP::Simple (unless -M and --add are not as synonymous as the documentation implies). LWP::Simple and it's dependencies (over 400 files) are added to the zip, but PAR can not find them in @INC. My guess is that since you can not add PAR.pm to a PAR file, that it is a special case and is instantiated using a different environment and a different @INC than anything else. I even tried putting a "use LWP::Simple" inside a BEGIN {} block in my script, which *seems* to be a step in the right direction - it no longer complained about LWP::Simple, but it then couldn't find LWP.pm, so I would add it to the BEGIN block, and so on until there were no errors, but "use PAR remote-URL" still couldn't find the remote module.
a pp generated exe ... not finding LWP::Simple.
Have you tried --add=LWP::Simple?
Either way, this sounds like either a bug, or just incompatible features. I think I'll just write my own routine to pre-fetch the needed PAR files using LWP::Simple::mirror and use local PAR files - that seems to work fine.
