comment on

Personally I'd just use your OS's package manager for the modules

Are you suggesting the OP rely on the OS's package repository? Or suggesting the OP create packages for deployment using the OS's package manager?

If the first, generally it is a bad idea for "non system" Perl applications to use the "system Perl" as updates are more likely to cause problems. It is better to leave the system Perl for OS's use and install one or more separate versions of Perl for non system applications.

If the second, I think it would be easier (and more portable) to deploy applications by creating the same type of package CPAN uses. The resulting tar.gz file can be copied to each server and the cpan command con be used to install it:

$ cpan
cpan> install myapp.tar.gz
[download]

Would even be possible for the OP to setup a CPAN-like archive and direct cpan to use that before using the actual CPAN archive.

In reply to Re^2: how to improve: use MODULE VERSION LIST by RonW
in thread how to improve: use MODULE VERSION LIST by smile4me

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.


No such thing as a small change
	PerlMonks