comment on

"perhaps it might be of benefit to provide (possibly as one or more tutorials or meditations) a comparison of cpanminus to other common CPAN clients, "

I'm working on something as a background task, which has a hefty section on this very subject. I'll keep you posted.

"and thinking that if one were experimenting with different CPAN clients how much space could be "wasted" in the process."

cpanm has it's advantages, one being speed, it's simply a lot faster. It's also much lighter on resources, where cpan dies, e.g. installing things on an embedded, or otherwise resource limited system.

In reply to Re^2: Should cpanminus be part of the standard Perl release? by marto
in thread Should cpanminus be part of the standard Perl release? by marto

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks