How to Install and Uninstall perl-Test-Harness.noarch Package on Red Hat Enterprise Linux 8 (RHEL 8)

Last updated: November 25,2024

1. Install "perl-Test-Harness.noarch" package

Please follow the instructions below to install perl-Test-Harness.noarch on Red Hat Enterprise Linux 8 (RHEL 8)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                perl-Test-Harness.noarch
            
                    
    
    Copied

2. Uninstall "perl-Test-Harness.noarch" package

Here is a brief guide to show you how to uninstall perl-Test-Harness.noarch on Red Hat Enterprise Linux 8 (RHEL 8):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                perl-Test-Harness.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the perl-Test-Harness.noarch package on Red Hat Enterprise Linux 8 (RHEL 8)

Last metadata expiration check: 1:55:16 ago on Mon Feb 26 15:59:38 2024.
Available Packages
Name : perl-Test-Harness
Epoch : 1
Version : 3.42
Release : 1.el8
Architecture : noarch
Size : 279 k
Source : perl-Test-Harness-3.42-1.el8.src.rpm
Repository : ubi-8-appstream-rpms
Summary : Run Perl standard test scripts with statistics
URL : http://search.cpan.org/dist/Test-Harness/
License : GPL+ or Artistic
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.