How to Install and Uninstall perl-CGI-Prototype.noarch Package on Fedora 36

Last updated: January 10,2025

1. Install "perl-CGI-Prototype.noarch" package

This guide covers the steps necessary to install perl-CGI-Prototype.noarch on Fedora 36


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                perl-CGI-Prototype.noarch
            
                    
    
    Copied

2. Uninstall "perl-CGI-Prototype.noarch" package

This guide covers the steps necessary to uninstall perl-CGI-Prototype.noarch on Fedora 36:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                perl-CGI-Prototype.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the perl-CGI-Prototype.noarch package on Fedora 36

Last metadata expiration check: 0:08:40 ago on Thu Sep 8 08:04:50 2022.
Available Packages
Name : perl-CGI-Prototype
Version : 0.9054
Release : 30.fc36
Architecture : noarch
Size : 35 k
Source : perl-CGI-Prototype-0.9054-30.fc36.src.rpm
Repository : fedora
Summary : Create a CGI application by subclassing
URL : https://metacpan.org/release/CGI-Prototype
License : GPL+ or Artistic
Description : The core of every CGI application seems to be roughly the same:
:
: * Analyze the incoming parameters, cookies, and URLs to determine the state
: of the application (let's call this "dispatch").
: * Based on the current state, analyze the incoming parameters to respond to
: any form submitted ("respond").
: * From there, decide what response page should be generated, and produce it
: ("render").
:
: CGI::Prototype creates a "Class::Prototyped" engine for doing all this, with
: the right amount of callback hooks to customize the process. Because I'm
: biased toward Template Toolkit for rendering HTML, I've also integrated that
: as my rendering engine of choice. And, being a fan of clean MVC designs, the
: classes become the controllers, and the templates become the views, with clean
: separation of responsibilities, and "CGI::Prototype" a sort of "archetypal"
: controller.