I also have to manage Perl scripts that get run on a variety of servers with various OS's (but they're all unix). I copy the actual perl script to each server. For CPAN modules, I use the "install local" option on one server, then I tar up that lib directory, and copy it to the others. Set the PERL5LIB env var to the path of this lib so that perl can find it. For modules that have binary parts and/or require compiling etc., I'd recommend building on the oldest OS, and copying out from there.
I would only use PAR::Packer if I needed to deploy to a Windose box for some reason. Don't install modules as root, since you might accidentally break your system perl (or change the behavior of scripts used by the OS). If I need to change something, I test on one machine, then push out the new version to the other s using rsync.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|