One of the options available to you while building Perl is whether or not it should maintain a grasp on 5.005* versions of your modules. Normally @INC contains just module directories specific to your version of Perl, but this doesn't have to be the case. Watch for "backward-compatibility" options during the configure process.

Normally (or at least this is how I understand it), modules will only put themselves in version-specific directories if there is a reason the module might not be compatible with other versions of Perl. Likewise, we have architecture-dependent directories for the same reason. In theory you can share your Perl library directory to systems using a variety of architectures and versions of Perl without worry, since everything that is unversioned should be compatible with all versions of Perl, and anything in an architecture-specific directory would only be valid for that architecture. (There are exceptions for stuff that links in external shared libraries, that might or might no be present on otherwise identical directories, or might be located in unexpected places.)

So basically, along that line, if you have stuff in a 5.005 directory, it might be there because there's a likelyhood that it's incompatible with 5.6 (though I don't actually know of many/any modules where this is actually the case), and this is sort of a hint that these modules need to be rebuilt for 5.6.

In reply to Re: Upgrading without losing modules? by Fastolfe
in thread Upgrading without losing modules? by chorg

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.