How to Install and Uninstall perl-strictures Package on openSUSE Leap

Last updated: June 24,2024

1. Install "perl-strictures" package

In this section, we are going to explain the necessary steps to install perl-strictures on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                perl-strictures
            
                    
    
    Copied

2. Uninstall "perl-strictures" package

In this section, we are going to explain the necessary steps to uninstall perl-strictures on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                perl-strictures
            
                    
    
    Copied

3. Information about the perl-strictures package on openSUSE Leap

Information for package perl-strictures:
----------------------------------------
Repository : Main Repository
Name : perl-strictures
Version : 2.000006-bp155.2.12
Arch : noarch
Vendor : openSUSE
Installed Size : 52.4 KiB
Installed : No
Status : not installed
Source package : perl-strictures-2.000006-bp155.2.12.src
Upstream URL : https://metacpan.org/release/strictures
Summary : Turn on strict and make most warnings fatal
Description :
I've been writing the equivalent of this module at the top of my code for
about a year now. I figured it was time to make it shorter.
Things like the importer in 'use Moose' don't help me because they turn
warnings on but don't make them fatal -- which from my point of view is
useless because I want an exception to tell me my code isn't
warnings-clean.
Any time I see a warning from my code, that indicates a mistake.
Any time my code encounters a mistake, I want a crash -- not spew to STDERR
and then unknown (and probably undesired) subsequent behaviour.
I also want to ensure that obvious coding mistakes, like indirect object
syntax (and not so obvious mistakes that cause things to accidentally
compile as such) get caught, but not at the cost of an XS dependency and
not at the cost of blowing things up on another machine.
Therefore, strictures turns on additional checking, but only when it thinks
it's running in a test file in a VCS checkout -- although if this causes
undesired behaviour this can be overridden by setting the
'PERL_STRICTURES_EXTRA' environment variable.
If additional useful author side checks come to mind, I'll add them to the
'PERL_STRICTURES_EXTRA' code path only -- this will result in a minor
version increase (e.g. 1.000000 to 1.001000 (1.1.0) or similar). Any fixes
only to the mechanism of this code will result in a sub-version increase
(e.g. 1.000000 to 1.000001 (1.0.1)).