Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Perl-Critic CPAN distribution.

Report information
The Basics
Id: 48004
Status: resolved
Priority: 0/
Queue: Perl-Critic

People
Owner: Nobody in particular
Requestors: LIMAONE [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in:
  • 1.109
  • 1.111
Fixed in:
  • 1.110_001
  • 1.112_001
  • 1.112_002
  • 1.113



Subject: CodeLayout::RequireTidyCode and missing Perl::Tidy
Hi, I think policies shouldn't turn off themselves silently if some dependencies are not installed - at least not at higher verbosity levels. A warning such as "Policy CodeLayout::RequireTidyCode deactivated because Perl::Tidy is not installed. Install Perl::Tidy or set [-CodeLayout::RequireTidyCode] to deactivate this policy." would be helpful. The author might not be aware that this policy exists and Test::Perl::Critic might fail if an user has the dependency installed. Thanks again for all your work on Perl::Critic! Markus
On Sun Jul 19 06:34:43 2009, LIMAONE wrote: Show quoted text
> I think policies shouldn't turn off themselves silently if some > dependencies are not installed - at least not at higher verbosity > levels.
Thanks for the suggestion. I'll put this on the TODO list. For what it's worth, Perl-Critic does warn you about missing optional dependencies when you build/install it. Show quoted text
> Test::Perl::Critic might fail if an user has the dependency installed.
We always recommend that you NOT ship any Perl-Critic tests in your distribution, or at least disable them by default. As you pointed out, there's no way of knowing what Policies someone has installed. And you don't want your distro's tests to fail just because of that. We see Perl-Critic as an author-only test.
I'm going to call this patched, since Perl::Tidy is no longer optional starting with Perl::Critic 1.110_001.