|
Posted by qtarokk on March 23, 2005, 4:56 pm
Please log in for more thread options
I am a beginner in Perl. hope it doesn't sound silly.
If i install a 3rd party module somewhere in @INC, then call it in my
own script. when I run my script on a different machine, do I need to
install that module on the 2nd machine too?
or, should i install the module in my "." directory, so i can just tar
up the whole thing and deploy it on another machine?
thanks in advance.
Paul
|
|
Posted by qtarokk on March 23, 2005, 6:58 pm
Please log in for more thread options
hmm, seems like it work.
I cp the .pm file locally to the same directory as my script, without
installing the module (make Makefile.pl.. etc). Within my script, i
call the module as it suggested, and it works fine.
so i can just tar up the whole directory and deploy it to other
machines.
not sure if this is the conventional way to do it. or any other better
way?
|
|
Posted by Jim Keenan on March 24, 2005, 2:54 am
Please log in for more thread options
qtarokk@gmail.com wrote:
> I am a beginner in Perl. hope it doesn't sound silly.
>
> If i install a 3rd party module somewhere in @INC, then call it in my
> own script. when I run my script on a different machine, do I need to
> install that module on the 2nd machine too?
>
Read up on @INC in:
perldoc perlvar
The item on @INC is, in my version at least, at approx. line 1278.
If the two machines are entirely unconnected, then, yes, you would have
to install the module on both machines.
If, however, the directory where you loaded the module is on a drive
accessible to both machines, then, no, you would not have to install the
module more than once.
jimk
|
|
Posted by John Bokma on March 24, 2005, 4:12 am
Please log in for more thread options
wrote:
> I am a beginner in Perl. hope it doesn't sound silly.
>
> If i install a 3rd party module somewhere in @INC, then call it in my
> own script. when I run my script on a different machine, do I need to
> install that module on the 2nd machine too?
Only if it's installed on the 2nd machine
> or, should i install the module in my "." directory, so i can just tar
> up the whole thing and deploy it on another machine?
That's one way to do it.
Also have a look at PAR.
--
John Small Perl scripts: http://johnbokma.com/perl/
Perl programmer available: http://castleamber.com/
Happy Customers: http://castleamber.com/testimonials.html
|
|
Posted by qtarokk on March 24, 2005, 12:03 am
Please log in for more thread options
hmm, is this why my python friend kept telling me "Perl's hard to
manage"...
guess those 3rd party module were made to run on individual machine,
but not with "massive deployment" in mind?
Paul
|
| Similar Threads | Posted | | GD modules | September 1, 2004, 8:20 am |
| Perl PDF modules - help please | August 11, 2004, 2:31 pm |
| installing modules? | September 29, 2005, 1:52 pm |
| Need new maintainers for my modules | January 8, 2005, 7:24 am |
| Installing modules | August 5, 2005, 8:32 pm |
| Captcha Modules | August 15, 2005, 5:35 pm |
| writing modules in 'c' | August 27, 2005, 3:18 pm |
| Modules with several packages | October 16, 2005, 10:50 am |
| Which Perl modules to use | January 25, 2006, 12:37 pm |
| Bundle::Modules | May 10, 2006, 12:16 am |
|
XML Sitemap