How to Install and Uninstall perl-AnyEvent-HTTP.noarch Package on Rocky Linux 9

Last updated: November 27,2024

1. Install "perl-AnyEvent-HTTP.noarch" package

This guide covers the steps necessary to install perl-AnyEvent-HTTP.noarch on Rocky Linux 9


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                perl-AnyEvent-HTTP.noarch
            
                    
    
    Copied

2. Uninstall "perl-AnyEvent-HTTP.noarch" package

In this section, we are going to explain the necessary steps to uninstall perl-AnyEvent-HTTP.noarch on Rocky Linux 9:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                perl-AnyEvent-HTTP.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the perl-AnyEvent-HTTP.noarch package on Rocky Linux 9

Last metadata expiration check: 0:46:10 ago on Fri Feb 16 06:49:52 2024.
Available Packages
Name : perl-AnyEvent-HTTP
Version : 2.25
Release : 7.el9
Architecture : noarch
Size : 44 k
Source : perl-AnyEvent-HTTP-2.25-7.el9.src.rpm
Repository : epel
Summary : Simple but non-blocking HTTP/HTTPS client
URL : https://metacpan.org/release/AnyEvent-HTTP
License : GPL+ or Artistic
Description : This module is an AnyEvent user, you need to make sure that you use and
: run a supported event loop.
:
: This module implements a simple, stateless and non-blocking HTTP client.
: It supports GET, POST and other request methods, cookies and more, all
: on a very low level. It can follow redirects supports proxies and
: automatically limits the number of connections to the values specified
: in the RFC.
:
: It should generally be a "good client" that is enough for most HTTP
: tasks. Simple tasks should be simple, but complex tasks should still be
: possible as the user retains control over request and response headers.
:
: The caller is responsible for authentication management, cookies (if the
: simplistic implementation in this module doesn't suffice), referrer and
: other high-level protocol details for which this module offers only
: limited support.