Re:Perl::Critic - Automatically review your code
by systems on Saturday June 29, 2013 @09:09PM
(#5964314)
when dealing with cpan, i think you should separate between the repository itself, which is surely more up to date than debian or ubuntu repos (because this is where debian or ubuntu pull from anyway)
and the command line interface, you have cpan, cpanp (cpan plus) and cpanm (cpan minus)
some cpan interfaces work better than others
Re:Perl::Critic - Automatically review your code
by Moto7451 on Sunday June 30, 2013 @03:53AM
(#5965062)
To update all packages use:
cpan upgrade /(.*)/
Re:Perl::Critic - Automatically review your code
by gnosis on Sunday June 30, 2013 @11:09AM
(#5966009)
That doesn't seem to work for me.
First, typing that in the shell gives me an error:
zsh: no matches found: /(.*)/
So, I tried typing: cpan upgrade '/(.*)/'
Which at least kept my shell from trying to expand the last argument, but cpan complained: Warning: Cannot install upgrade, don't know what it is.
Try the command
i /upgrade/
to find objects with matching identifiers.
Sorry, install with a regular expression is only supported when unambiguous.
Rejecting argument '/(.*)/'
So, instead at the shell I just typed: cpan
Then, at the cpan[1]> prompt, I typed: upgrade
That seemed to work.
Also I assume that cpan packages reflected through apt will be updated with apt-get update, while cpan has no similar update-all mechanism (AFAIK).
One advantage of using cpan is that if you're developing on a Mac and deploying on a Debian distro you can use the same commands on both systems to pull in the packages you need.