Start your program with something like: 
#!/opt/perl/bin/perl -w

use strict;
use warnings;

use FindBin;

BEGIN {
    delete $INC {'File/Spec.pm'};
    delete $INC {'File/Spec/Unix.pm'};
}

use vars '$old_W';

BEGIN {$old_W = $^W; $^W = 0}
use libs '....';     # The 'cousin' directory here.
use File::Spec;
BEGIN {$^W = $old_W}

[download]
File::Spec might pull in something else on a different OS. Experiment. The key thing here is the deletion from %INC, which if we leave %INC as it is, will prevent use and require from recompiling a module.

Note that you'll get warnings if File::Spec would do a use warnings.

-- Abigail

In reply to Re: Forcing use of newer (local) version of core module by Abigail
in thread Forcing use of newer (local) version of core module by jwd

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.