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

Last updated: June 03,2024

1. Install "perl-Text-RecordParser.noarch" package

This guide covers the steps necessary to install perl-Text-RecordParser.noarch on Red Hat Enterprise Linux 8 (RHEL 8)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                perl-Text-RecordParser.noarch
            
                    
    
    Copied

2. Uninstall "perl-Text-RecordParser.noarch" package

In this section, we are going to explain the necessary steps to uninstall perl-Text-RecordParser.noarch on Red Hat Enterprise Linux 8 (RHEL 8):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                perl-Text-RecordParser.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

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

Last metadata expiration check: 1:57:36 ago on Mon Feb 26 15:59:38 2024.
Available Packages
Name : perl-Text-RecordParser
Version : 1.6.5
Release : 18.el8
Architecture : noarch
Size : 51 k
Source : perl-Text-RecordParser-1.6.5-18.el8.src.rpm
Repository : epel
Summary : Read record-oriented files
URL : https://metacpan.org/release/Text-RecordParser
License : GPLv2
Description : This module is for reading record-oriented data in a delimited text file.
: The most common example have records separated by newlines and fields
: separated by commas or tabs, but this module aims to provide a consistent
: interface for handling sequential records in a file however they may be
: delimited. Typically this data lists the fields in the first line of the
: file, in which case you should call bind_header to bind the field name (or
: not, and it will be called implicitly). If the first line contains data,
: you can still bind your own field names via bind_fields. Either way, you
: can then use many methods to get at the data as arrays or hashes.