comment on

Do not mess with the OS-installed perl.

Longer answer: Unless trying to make your application installable by all, install a local perl distribution into its own location that your application has been tested with, including all required modules and configurations. This allows you to decouple your application from the OS-required version of perl, minimizes the chance of breaking the OS by touching the OS-required version of perl, and minimize the chance of OS upgrades breaking your application (for the same reason).

(Update) Use the build toolchain. Configure the prerequisites in your Makefile.PL or Build.PL, and use cpanm to build a self-contained library directory of the requirements. You should include everything that your application directly uses in the prerequisites (not just the top level module, and not modules that you don't directly use). You then have a set of steps by which you can target any additional platforms (or CPAN updates, etc). See also:

--MidLifeXis

In reply to Re: Move Perl modules to new CentOS VPS by MidLifeXis
in thread Move Perl modules to new CentOS VPS by monx

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.


Think about Loose Coupling
	PerlMonks