How to Install and Uninstall perl-Test2-Tools-PerlCritic.noarch Package on Fedora 39
Last updated: November 21,2024
1. Install "perl-Test2-Tools-PerlCritic.noarch" package
This tutorial shows how to install perl-Test2-Tools-PerlCritic.noarch on Fedora 39
$
sudo dnf update
Copied
$
sudo dnf install
perl-Test2-Tools-PerlCritic.noarch
Copied
2. Uninstall "perl-Test2-Tools-PerlCritic.noarch" package
Here is a brief guide to show you how to uninstall perl-Test2-Tools-PerlCritic.noarch on Fedora 39:
$
sudo dnf remove
perl-Test2-Tools-PerlCritic.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-Test2-Tools-PerlCritic.noarch package on Fedora 39
Last metadata expiration check: 0:42:48 ago on Thu Mar 7 17:44:52 2024.
Available Packages
Name : perl-Test2-Tools-PerlCritic
Version : 0.04
Release : 8.fc39
Architecture : noarch
Size : 21 k
Source : perl-Test2-Tools-PerlCritic-0.04-8.fc39.src.rpm
Repository : fedora
Summary : Testing tools to enforce Perl::Critic policies
URL : https://metacpan.org/release/Test2-Tools-PerlCritic
License : GPL+ or Artistic
Description : Test for Perl::Critic violations using Test2. Although this testing tool
: uses the Test2 API instead of the older Test::Builder API, the primary
: motivation is to provide output in a more useful form. That is policy
: violations are grouped by policy class, and the policy class name is
: clearly displayed as a diagnostic. The author finds the former more useful
: because he tends to address one type of violation at a time. The author
: finds the latter more useful because he tends to want to lookup or adjust
: the configuration of the policy as he is addressing violations.
Available Packages
Name : perl-Test2-Tools-PerlCritic
Version : 0.04
Release : 8.fc39
Architecture : noarch
Size : 21 k
Source : perl-Test2-Tools-PerlCritic-0.04-8.fc39.src.rpm
Repository : fedora
Summary : Testing tools to enforce Perl::Critic policies
URL : https://metacpan.org/release/Test2-Tools-PerlCritic
License : GPL+ or Artistic
Description : Test for Perl::Critic violations using Test2. Although this testing tool
: uses the Test2 API instead of the older Test::Builder API, the primary
: motivation is to provide output in a more useful form. That is policy
: violations are grouped by policy class, and the policy class name is
: clearly displayed as a diagnostic. The author finds the former more useful
: because he tends to address one type of violation at a time. The author
: finds the latter more useful because he tends to want to lookup or adjust
: the configuration of the policy as he is addressing violations.