This does appear to be a third possible solution, but the CPAN perldoc makes me a little weary about it. Specifically: In fine tuned environments UNINST=1 can cause damage.

1)

    I installed a new version of module X but CPAN keeps saying, I hav
+e the old version installed

    Most probably you do have the old version installed. This can happ
+en if a module installs itself into a different directory in the @INC
+ path than it was previously installed. This is not really a CPAN.pm 
+problem, you would have the same problem when installing the module m
+anually. The easiest way to prevent this behaviour is to add the argu
+ment UNINST=1 to the make install call, and that is why many people a
+dd this argument permanently by configuring

      o conf make_install_arg UNINST=1

2)

    So why is UNINST=1 not the default?

    Because there are people who have their precise expectations about
+ who may install where in the @INC path and who uses which @INC array
+. In fine tuned environments UNINST=1 can cause damage.

[download]

In reply to Re^3: Upgrading Core Modules Using CPAN - Best Practice? by stocks29
in thread Upgrading Core Modules Using CPAN - Best Practice? by stocks29

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.