How to Install and Uninstall perl-Test-InDistDir Package on openSUSE Leap

Last updated: November 22,2024

1. Install "perl-Test-InDistDir" package

Here is a brief guide to show you how to install perl-Test-InDistDir on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                perl-Test-InDistDir
            
                    
    
    Copied

2. Uninstall "perl-Test-InDistDir" package

This guide let you learn how to uninstall perl-Test-InDistDir on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                perl-Test-InDistDir
            
                    
    
    Copied

3. Information about the perl-Test-InDistDir package on openSUSE Leap

Information for package perl-Test-InDistDir:
--------------------------------------------
Repository : Main Repository
Name : perl-Test-InDistDir
Version : 1.112071-bp155.2.12
Arch : noarch
Vendor : openSUSE
Installed Size : 7.3 KiB
Installed : No
Status : not installed
Source package : perl-Test-InDistDir-1.112071-bp155.2.12.src
Upstream URL : http://search.cpan.org/dist/Test-InDistDir/
Summary : test environment setup for development with IDE
Description :
This module helps run test scripts in IDEs like Komodo.
When running test scripts in an IDE i have to set up a project file
defining the dist dir to run tests in and a lib dir to load additional
modules from. Often I didn't feel like doing that, especially when i only
wanted to do a small patch to a dist. In those cases i added a BEGIN block
to mangle the environment for me.
This module basically is that BEGIN block. It automatically moves up one
directory when it cannot see the test script in "t/$scriptname" and
includes 'lib' in @INC when there's no blib present. That way the test ends
up with almost the same environment it'd get from EUMM/prove/etc., even
when it's actually run inside the t/ directory.
At the same time it will still function correctly when called by
EUMM/prove/etc., since it does not change the environment in those cases.