From: Michael Corral (email_suppressed_at_lugwash.org)
Date: Mon 10-Jul-2006 01:40:02 PM EDT
Monsieur Rob Duncan a ecrit:
> On Mon, July 10, 2006 7:45 am, Robert Seward wrote:
>> It would be really cool if Perl had "par" files and a "modulepath", so I
>> can gather up all my external modules and have them integrated into a
>> home directory with my Perl applications.
>>
>> My Perl application could live happily for many years, without fear of
>> breaking when I do a system wide Perl upgrade.
>>
>> Is there an obvious way to do this, that I don't know about?
>
> http://use.perl.org/articles/02/11/02/224205.shtml?tid=5
> http://search.cpan.org/~AUTRIJUS/PAR-0.89/lib/PAR.pm
> http://search.cpan.org/~autrijus/PAR-0.89/script/pp
Hmm, PAR.pm doesn't appear to be included as part of standard Perl.
So you'd have to install that module for everyone who wanted to use
the PAR files. Not built-in like in Java, but OK it's not too bad.
However, looking through the PAR.pm source code
<http://search.cpan.org/src/AUTRIJUS/PAR-0.89/lib/PAR.pm>, it
appears that PAR.pm just unzips the PAR file contents into a
temp directory (under c:\temp or /tmp by default) and then uses
the files from there (unless I'm reading the source incorrectly).
I'm not sure I like the idea of using a temp directory for this.
It doesn't look like the module even checks if there is enough
disk space in the temp directory (unless one of the other modules
that it uses does so). I can see some problems with this.
Michael
-- *** Sent from [e-mail suppressed] *** http://www.lugwash.org to unsubscribe: `echo "unsubscribe" | mail [e-mail suppressed]`
This archive was generated by hypermail 2.1.5 : Tue 01-Aug-2006 01:00:02 AM EDT