Speaking of which raises an oft discussed matter: OS-specific-package vs CPAN.pm! Personally I've seen this discussed in CRUX ml to which I'm subscribed (yes, I'm a CRUX user, of course!) - and I think that a solution that would satisfy both those who want to keep track of everything that is installed on their system and of those who prefer to use Perl's specific tool would be that of patching CPAN.pm itself as of to create a (say) CRUX package on the fly before installing. A solution that would be slightly redundant indeed, but that as I implied would give the best of both words.

The proposed solution would be particularly simple as of CRUX due to the KISS nature of its packages, but I think it would be doable with other distros as well.

The key point: however I'm not sure how easy and most importantly how {reliable,maintainable} patching CPAN.pm would be, so I wonder if it could not expose suitable "hooks" for such an "enhancement" instead, say something along the lines of

perl -MCPAN=CRUX -e shell
where of course there should be an OS-specific CRUX.pm available somewhere in @LIB, or something like that...

In reply to [side note] Re: Install using perl -MCPAN -e 'install module' doesn't work by blazar
in thread Install using perl -MCPAN -e 'install module' doesn't work by jbrugger

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.