News for hackers. Stuff that matters.
Re:Perl::Critic - Automatically review your code by ratsbane on Saturday June 29, 2013 @08:23PM (#5964210)
For Debian/Ubuntu: sudo apt-get install libtest-perl-critic-perl
Re:Perl::Critic - Automatically review your code by nnutter on Saturday June 29, 2013 @09:37PM (#5964378)
libperl-critic-perl is the core Perl Critic. libtest-perl-critic-perl is for using Perl Critic in tests.
Re:Perl::Critic - Automatically review your code by systems on Saturday June 29, 2013 @08:36PM (#5964250)
i dont see how the debian maintainers can keep up with cpan, just use cpan for perl

generally speaking, i find the centralized packaging system flawed ... because on the long term its unsustainable

cpan is decentralized by the way, because module makers package their modules themselves for cpan

Re:Perl::Critic - Automatically review your code by ratsbane on Saturday June 29, 2013 @08:45PM (#5964274)
I go back and forth on this. Aptitude seems more reliable in general than cpan, at least in the sense that cpan installations fail more frequently than apt.

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.

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.
Re:Perl::Critic - Automatically review your code by Moto7451 on Sunday June 30, 2013 @12:25PM (#5966266)
Sorry meant the CPAN shell. Should have reproduced the prompt better. Also it does appear that the regex isn't required any longer. That's certainly nice.
Re:Perl::Critic - Automatically review your code by nnutter on Saturday June 29, 2013 @09:38PM (#5964381)
There are trade-offs. There is no perfect solution.
Re:Perl::Critic - Automatically review your code by csirac2 on Sunday June 30, 2013 @03:12AM (#5964992)
That's why I just use cpan2deb. There's a few modules that won't package properly with it, I should file some bugs.

I also use cpanm when I have a need to be separate from vendor, but generally in the worst-case admins prefer to only maintain one set of perl/cpan rather than two.

Re:Perl::Critic - Automatically review your code by gnosis on Saturday June 29, 2013 @09:01PM (#5964301)
"i find the centralized packaging system flawed ... because on the long term its unsustainable"

Could you elaborate on why you think this?

Re:Perl::Critic - Automatically review your code by systems on Saturday June 29, 2013 @09:23PM (#5964351)
i hope engaging in this clearly off topic, wont offend others

linux and foss rely on volunteer effort, therefore efficiency matters a lot, inefficient system will loose volunteers and momentum, i think its surprising the system lasted for so long , but then i believe the number of surviving distros is in decline and even less so the number of package management system

anyway, maybe my usage of the word centralized and decentralized term is wrong

cpan can be viewed as centralized, it is a single storage space for all modules

i just believe that is too much waste, in having to repackage each application to different systems, there must be a better way, where the effort will be more efficient and require less resources

maybe the opposite of what i said is true, maybe we need to centralize over one package system to reduce the effort, or in other, maybe we need we centralized over a single system and repo, to be able to decentralize the effort

Re:Perl::Critic - Automatically review your code by berntb on Sunday June 30, 2013 @04:16AM (#5965094)
I thought most people would have as main reason to not mix their own stuff with the system Perl?!

And you want multiple Perls installed, anyway. Backward compatibility is a target in the Perl world, but stay safe... ("This is the versions at the job servers. This is what I do my hobbies with. Also, I need to keep a 5.8.8 Perl, to make certain so X works with that golden oldie.")