How to Install and Uninstall libcriticism-perl Package on Ubuntu 20.10 (Groovy Gorilla)

Last updated: December 24,2024

1. Install "libcriticism-perl" package

Please follow the guidance below to install libcriticism-perl on Ubuntu 20.10 (Groovy Gorilla)


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                libcriticism-perl
            
                    
    
    Copied

2. Uninstall "libcriticism-perl" package

Please follow the guidelines below to uninstall libcriticism-perl on Ubuntu 20.10 (Groovy Gorilla):


    
        
            $
        

        
            
                sudo apt remove
            
                        
                libcriticism-perl
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the libcriticism-perl package on Ubuntu 20.10 (Groovy Gorilla)

Package: libcriticism-perl
Architecture: all
Version: 1.02-2
Priority: optional
Section: universe/perl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 50
Depends: perl
Recommends: libperl-critic-perl
Filename: pool/universe/libc/libcriticism-perl/libcriticism-perl_1.02-2_all.deb
Size: 9354
MD5sum: 161e46461c942c0dd0c62d65f1433c10
SHA1: c043af5baa16cc50260d7d849cbae87e9b209c13
SHA256: 530b52c8bc163ef5c06f90b1aa1520faf878703ce7b87cfc3395177299e6609f
SHA512: cfed0dd8b4cf4e795105ac0bea44e66b8501b20a2c70f847c8be58e17f06c87b378b7437ed86d1853459a3a640d6782eed337a1940454091f940b0f653b7dcf5
Homepage: https://metacpan.org/release/criticism
Description-en: Perl pragma to enforce coding standards and best-practices
The cristicism pragma enforces coding standards and promotes best-practices
by running your file through Perl::Critic before every execution. In a
production system, this usually isn't feasible because it adds a lot of
overhead at start-up. If you have a separate development environment,
you can effectively bypass the "criticism" pragma by not installing
Perl::Critic in the production environment. If Perl::Critic can't be
loaded, then "criticism" just fails silently.
Description-md5: 318f9732aaf59c61f884703be29cb611