Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

Re: Detecting failures easily/obviously with cpanm

by stevieb (Canon)
on Jun 16, 2022 at 16:12 UTC ( #11144803=note: print w/replies, xml ) Need Help??

in reply to Detecting failures easily/obviously with cpanm

cpanm -q Module::Name can help. The -q (aka --quiet) flag reduces the output to list only the distribution installs attempted, and their success or fail status.

Typically what I do though is just re-run the cpanm command again, as it'll skip over all the successful dists, and focus squarely on the failed ones making them easy to identify.

Replies are listed 'Best First'.
Re^2: Detecting failures easily/obviously with cpanm
by hippo (Bishop) on Jun 16, 2022 at 21:51 UTC

    I had considered the option of just re-running the whole lot to make the failures stand out, however that does make my inefficiency-spidey-sense start tingling. One of the modules in today's bundle was Mail::Spamassassin for instance and that takes several minutes to run its test suite. Still worth bearing in mind, though.

    Thanks for the pointer to -q - I will definitely give that one a go.


Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11144803]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (2)
As of 2023-03-26 05:13 GMT
Find Nodes?
    Voting Booth?
    Which type of climate do you prefer to live in?

    Results (63 votes). Check out past polls.