How to Install and Uninstall perl-Text-RecordParser Package on openSUSE Leap

Last updated: December 25,2024

1. Install "perl-Text-RecordParser" package

In this section, we are going to explain the necessary steps to install perl-Text-RecordParser on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                perl-Text-RecordParser
            
                    
    
    Copied

2. Uninstall "perl-Text-RecordParser" package

In this section, we are going to explain the necessary steps to uninstall perl-Text-RecordParser on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                perl-Text-RecordParser
            
                    
    
    Copied

3. Information about the perl-Text-RecordParser package on openSUSE Leap

Information for package perl-Text-RecordParser:
-----------------------------------------------
Repository : Main Repository
Name : perl-Text-RecordParser
Version : 1.6.5-bp155.3.8
Arch : noarch
Vendor : openSUSE
Installed Size : 92.9 KiB
Installed : No
Status : not installed
Source package : perl-Text-RecordParser-1.6.5-bp155.3.8.src
Upstream URL : http://search.cpan.org/dist/Text-RecordParser/
Summary : Read Record-Oriented Files
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.