If some of the modules you are using are XS modules and the machines have different perl versions, then you may not be able to simply copy files even if you knew the @INC locations.
Since production is a locked down environment PPM is out of the question.
Do you mean that using PPM to retrieve remote files is out of the question or that using PPM at all is out of the question? Assuming all your machines are the same platform and can all use binary compatible XS modules, and assuming it's just the remote access that is stopping you, you can download the .ppds onto your development machine, write a script that successively calls PPM on all of the local .ppds, then distribute the script + .ppds to all the production machines. Running the script on each machine will use that machine's perl and @INC to do the local install but won't have to connect to the internet.
You could also do something similar with CPAN.pm, but that would assume that CPAN.pm is configured on all of the production machines.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.