Path to this page:
Subject: CVS commit: pkgsrc/devel/p5-Test-Perl-Critic
From: Makoto Fujiwara
Date: 2015-02-17 07:50:00
Message id: 20150217065000.3D54898@cvs.netbsd.org
Log Message:
(pkgsrc)
- Add PERL5_MODULE_TYPE= Module::Build
(upstream)
- Update to 1.03
---------------
[1.03] Released on 2015-02-03
all_critic_ok() will now run tests in parallel over multiple cores. So if
you have 8 cores, your Perl::Critic tests could run 8x faster. However,
the actual performance depends on the size and shape of your code base and
your Perl::Critic configuration. Thank you Mario Roy for writing the
wonderful MCE module that makes this all possible!
If you're using the critic_ok() function directly (perhaps because you
want more control over which files are tested) then you won't see any
performance boost. I recommend gathering your list of files first, and
then passing the list to all_critic_ok().
The deprecated function all_code_files() has now been removed from
Test::Perl::Critic. Use Perl::Critic::Utils::all_perl_files() instead.
Files: