This website works better with JavaScript.
Explore
Help
Sign In
rpms
/
perl-Test-Perl-Critic
Watch
21
Star
0
Fork
You've already forked perl-Test-Perl-Critic
0
Code
Issues
Pull Requests
Packages
Projects
Releases
Wiki
Activity
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
b6669d8d45
i9ce
i9
epel9
changed/i9/perl-Test-Perl-Critic-1.04-18.el9
changed/i9ce/perl-Test-Perl-Critic-1.04-14.el9
imports/e9/perl-Test-Perl-Critic-1.04-14.el9
Branches
Tags
${ item.name }
Create tag
${ searchTerm }
Create branch
${ searchTerm }
from 'b6669d8d45'
${ noResults }
perl-Test-Perl-Critic
/
sources
2 lines
63 B
Raw
Normal View
History
Unescape
Escape
Update to 1.03 - New upstream release 1.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. - 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. - Classify buildreqs by usage - Drop obsoletes/provides for old -tests package - Use %license where possible
10 years ago
b10da607ed6c6c07eba99e48ce77d88a Test-Perl-Critic-1.03.tar.gz