Out of curiosity, do you need to keep your scripts as Perl scripts? If not, here's another approach that you can consider. Use something like pp from PAR::Packer to bundle your Perl script into a stand-along executable.

One advantage of that approach is that you don't have to manage Perl environments (versions of Perl installed, which modules are installed, which versions of modules installed, etc.) on multiple systems. Instead, you just manage your development Perl environment and distribute stand-alone executable files. Of course, one drawback is end users will not be able to modify the code as easily (which could be a good thing in certain situations).

If you still need/want to keep your scripts as Perl scripts, there's two other approaches that you can consider. You can use App::FatPacker to "pack your dependencies onto your script file", but I don't think that it will work for XS based modules.

If all of the systems have access to a file server, you can put a Perl installation (such as portable Strawberry Perl) on the file server. The other systems then can map a drive to the file server and use that Perl installation.

Just tossing out some ideas about alternative approaches.

In reply to Re: How to handle modules across different versions by dasgar
in thread How to handle modules across different versions by ksublondie

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.