How to Install and Uninstall perl-IO-stringy.noarch Package on CentOS 7 / RHEL 7

Last updated: April 28,2024

1. Install "perl-IO-stringy.noarch" package

This tutorial shows how to install perl-IO-stringy.noarch on CentOS 7 / RHEL 7


    
        
            $
        

        
            
                sudo yum makecache
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo yum install
            
                        
                perl-IO-stringy.noarch
            
                    
    
    Copied

2. Uninstall "perl-IO-stringy.noarch" package

This is a short guide on how to uninstall perl-IO-stringy.noarch on CentOS 7 / RHEL 7:


    
        
            $
        

        
            
                sudo yum remove 
            
                        
                perl-IO-stringy.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo yum autoremove
            
                    
    
    Copied

3. Information about the perl-IO-stringy.noarch package on CentOS 7 / RHEL 7

Installed Packages
Name : perl-IO-stringy
Arch : noarch
Version : 2.110
Release : 22.el7
Size : 130 k
Repo : installed
From repo : base
Summary : I/O on in-core objects like strings and arrays for Perl
URL : http://search.cpan.org/dist/IO-stringy/
License : GPL+ or Artistic
Description : This toolkit primarily provides modules for performing both
: traditional and object-oriented I/O) on things *other* than normal
: filehandles; in particular, IO::Scalar, IO::ScalarArray, and
: IO::Lines.
:
: In the more-traditional IO::Handle front, we have IO::AtomicFile,
: which may be used to painlessly create files that are updated
: atomically.
:
: And in the "this-may-prove-useful" corner, we have IO::Wrap, whose
: exported wraphandle() function will clothe anything that's not a
: blessed object in an IO::Handle-like wrapper... so you can just
: use OO syntax and stop worrying about whether your function's
: caller handed you a string, a globref, or a FileHandle.