How to Install and Uninstall perl-POE-Component-SimpleLog.noarch Package on Fedora 39

Last updated: November 27,2024

1. Install "perl-POE-Component-SimpleLog.noarch" package

This guide covers the steps necessary to install perl-POE-Component-SimpleLog.noarch on Fedora 39


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                perl-POE-Component-SimpleLog.noarch
            
                    
    
    Copied

2. Uninstall "perl-POE-Component-SimpleLog.noarch" package

Please follow the step by step instructions below to uninstall perl-POE-Component-SimpleLog.noarch on Fedora 39:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                perl-POE-Component-SimpleLog.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the perl-POE-Component-SimpleLog.noarch package on Fedora 39

Last metadata expiration check: 3:56:28 ago on Thu Mar 7 17:44:52 2024.
Available Packages
Name : perl-POE-Component-SimpleLog
Version : 1.05
Release : 40.fc39
Architecture : noarch
Size : 19 k
Source : perl-POE-Component-SimpleLog-1.05-40.fc39.src.rpm
Repository : fedora
Summary : A simple logging system for POE
URL : https://metacpan.org/release/POE-Component-SimpleLog
License : GPL+ or Artistic
Description : This module is a vastly simplified logging system that can do nice stuff.
: Think of this module as a dispatcher for various logs.
:
: This module *DOES NOT* do anything significant with logs, it simply routes
: them to the appropriate place ( Events )
:
: You register a log that you are interested in, by telling SimpleLog the target
: session and target event. Once that is done, any log messages your program
: generates ( sent to SimpleLog of course ) will be massaged, then sent to the
: target session / target event for processing.
:
: This enables an interesting logging system that can be changed during runtime
: and allow pluggable interpretation of messages.