How to Install and Uninstall perl-DBIx-Introspector.noarch Package on Fedora 38

Last updated: October 12,2024

1. Install "perl-DBIx-Introspector.noarch" package

This guide covers the steps necessary to install perl-DBIx-Introspector.noarch on Fedora 38


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                perl-DBIx-Introspector.noarch
            
                    
    
    Copied

2. Uninstall "perl-DBIx-Introspector.noarch" package

Please follow the steps below to uninstall perl-DBIx-Introspector.noarch on Fedora 38:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                perl-DBIx-Introspector.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the perl-DBIx-Introspector.noarch package on Fedora 38

Last metadata expiration check: 5:42:27 ago on Sat Mar 16 16:59:57 2024.
Available Packages
Name : perl-DBIx-Introspector
Version : 0.001005
Release : 12.fc38
Architecture : noarch
Size : 30 k
Source : perl-DBIx-Introspector-0.001005-12.fc38.src.rpm
Repository : fedora
Summary : Detect what database you are connected to
URL : https://metacpan.org/release/DBIx-Introspector
License : GPL+ or Artistic
Description : DBIx::Introspector is a module factored out of the DBIx::Class database
: detection code. Most code that needs to detect which database it is
: connected to assumes that there is a one-to-one mapping from database
: drivers to database engines. Unfortunately reality is rarely that simple.
: For instance, DBD::ODBC is typically used to connect to SQL Server, but
: ODBC can be used to connect to PostgreSQL, MySQL, and Oracle. Additionally,
: while ODBC is the most common way to connect to SQL Server, it is not the
: only option, as DBD::ADO can also be used.