Two more annoyances for you.

First, if the first CPAN mirror is down, with every single file CPAN fetches, you have to wait for it to rediscover that it can't fetch from that mirror. Why not have it on the next file rotate its list of mirrors so that it first tries the one that actually worked last time?

Second, on Ubuntu if I do sudo perl -MCPAN -e shell, the crypto bit gets all unhappy because root tries to access my user's keychain and decides it shouldn't. I have to (sudo su; perl -MCPAN -e shell) instead. Very minor, but if I'm listing annoyances, why not list it?

In reply to Re: [rant] Of the suckage of the CPAN shell by tilly
in thread [rant] Of the suckage of the CPAN shell by Anonymous Monk

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.