the PERLLIB environment variable captured at the customer site has over 430 directory entries.

I can't be the only one who read that (twice to make sure I hadn't mis-read) and immediately thought how impressively horrendous it is. You have my sympathy.

what would be the best method to verify that the captured Perl environment at the customer site unpacks and runs smoothly on my employer's network?

Obvious answer: run the test suite. Now I'm going to assume that an organisation that has ended up with 430 entries in $PERLLIB probably doesn't have a test suite. So your first task is to write one. I would start by writing a test which just compiles everything in turn. That way you can run the test, keep adding to @INC or whatever needs to be done to get things to compile without breaking the ones you've already fixed. This will be a lot of work but it's sure to pay off in the end.

Actually, I posted this Q on Stack Overflow and the first response was to post here.

That's fine but if you could link to that SOQ then it will save possible duplication of effort in replying. Thanks.

In reply to Re: How to manage the transfer of large Perl environments from one network to another by hippo
in thread How to manage the transfer of large Perl environments from one network to another by fiddler42

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.