How to Install and Uninstall perl-Test-Harness.noarch Package on Fedora 39
Last updated: January 20,2025
1. Install "perl-Test-Harness.noarch" package
This guide covers the steps necessary to install perl-Test-Harness.noarch on Fedora 39
$
sudo dnf update
Copied
$
sudo dnf install
perl-Test-Harness.noarch
Copied
2. Uninstall "perl-Test-Harness.noarch" package
Please follow the guidance below to uninstall perl-Test-Harness.noarch on Fedora 39:
$
sudo dnf remove
perl-Test-Harness.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-Test-Harness.noarch package on Fedora 39
Last metadata expiration check: 4:46:17 ago on Thu Mar 7 17:44:52 2024.
Available Packages
Name : perl-Test-Harness
Epoch : 1
Version : 3.48
Release : 1.fc39
Architecture : noarch
Size : 275 k
Source : perl-Test-Harness-3.48-1.fc39.src.rpm
Repository : updates
Summary : Run Perl standard test scripts with statistics
URL : https://metacpan.org/release/Test-Harness
License : GPL-1.0-or-later OR Artistic-1.0-Perl
Description : This package allows tests to be run and results automatically aggregated and
: output to STDOUT.
:
: Although, for historical reasons, the Test-Harness distribution takes its name
: from this module it now exists only to provide TAP::Harness with an interface
: that is somewhat backwards compatible with Test::Harness 2.xx. If you're
: writing new code consider using TAP::Harness directly instead.
Available Packages
Name : perl-Test-Harness
Epoch : 1
Version : 3.48
Release : 1.fc39
Architecture : noarch
Size : 275 k
Source : perl-Test-Harness-3.48-1.fc39.src.rpm
Repository : updates
Summary : Run Perl standard test scripts with statistics
URL : https://metacpan.org/release/Test-Harness
License : GPL-1.0-or-later OR Artistic-1.0-Perl
Description : This package allows tests to be run and results automatically aggregated and
: output to STDOUT.
:
: Although, for historical reasons, the Test-Harness distribution takes its name
: from this module it now exists only to provide TAP::Harness with an interface
: that is somewhat backwards compatible with Test::Harness 2.xx. If you're
: writing new code consider using TAP::Harness directly instead.