Re^2: How do I keep Red Hat perl RPM updates from damaging our local module upgrades and installations?

We are stuck with the Red Hat RPM for now and the foreseeable future. Installing our own perl is considered to disruptive.

Site_perl is first in @INC. When I access the CGI.pm element of the @INC hash in my test below it returns the /usr/lib/perl5/site_perl path and not the /usr/lib/perl5/5.8.8 path which also has CGI.pm.

CGI.pm exists in two locations.
# ls  /usr/lib/perl5/5.8.8/CGI.pm  /usr/lib/perl5/site_perl/5.8.8/CGI.
+pm
/usr/lib/perl5/5.8.8/CGI.pm  /usr/lib/perl5/site_perl/5.8.8/CGI.pm

Which CGI.pm are we using?
# perl -MCGI -le 'print $INC{"CGI.pm"}'
/usr/lib/perl5/site_perl/5.8.8/CGI.pm

# perl -V | tail -10
  @INC:
    /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi
    /usr/lib/perl5/site_perl/5.8.8
    /usr/lib/perl5/site_perl
    /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi
    /usr/lib/perl5/vendor_perl/5.8.8
    /usr/lib/perl5/vendor_perl
    /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi
    /usr/lib/perl5/5.8.8
    .
[download]

Comment on Re^2: How do I keep Red Hat perl RPM updates from damaging our local module upgrades and installations? Download Code