Thanks kcott for the reply, I'll try to clarify:

Once the CTB folks have added a new feature, using a new or improved CPAN module, they certainly want it to go into production. Thus, they are willing to update the code to:

use autodie 2.29

Where I run into problem is that Perl does not find version 2.29 given the order of the default @INC. Remeber, the RTB folks are still looking for autodie 2.23 in the core perl paths when the interpreter was compiled; but, the CTB folks want to get the new one. Unfortunately, when compiling Perl with the otherlibdirs option (to include additional locations), it adds the new locations to the end of @INC.

So it seems, I am left with no other choice but to manipulate the @INC order in the code. Typically, once tools make their way into production, the owner (unix user) of scripts has a very limited shell environment (think apache user or www user). So relying on PERL5LIB, while okay for testing, is not so good for production.

Thus, your slicing the INC is an option. BTW, why is the '.' location not good in the @INC?

Smile
Steve

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

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.