I have a strict production environment. It is running a standard Perl installation. That is, it has no CPAN modules installed. I would like to package CPAN module installations into our release procedures. I can use PPM or anything else to install packages on on development machine.
For production I would mike to just copy the correct files to the proper Perl directories in production. Is there one static directory that collects all CPAN files that get downloaded? Is this directory or directories guaranteed to have the same name and location in hierarchy for different Perl versions?
Maybe there is an easier way to package an installation. Does anyone have other suggestions? Since production is a locked down environment PPM is out of the question. I can use PPM or anything else in a development environment and then package up the modules for installation though. Any ideas?
Thanks.
-
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.
|