Thanks to all three respondents. What happened was that @INC in my 5.10.1 didn't include all of the directories from past versions, such that (as I found out later) I needed an update of Term::ReadLine::Gnu to make one of my scripts work right. I thought the problems was with Term::ReadLine, and didn't check its status. Naturally, when I just said install, perl -MCPAN said it was up to date, so I tried to force it.

Perl -MCPAN's response of trying to unpack perl was mysterious at the end of a long day. Later I finally got @INC in 5.10.1 right, so that all past module directories are now present and in the right order.

In reply to Re^2: CPAN local data corrupted by cmac
in thread CPAN local data corrupted by cmac

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.