How to Install and Uninstall autoconf-archive Package on openSUSE Leap

Last updated: November 26,2024

1. Install "autoconf-archive" package

This guide covers the steps necessary to install autoconf-archive on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                autoconf-archive
            
                    
    
    Copied

2. Uninstall "autoconf-archive" package

This is a short guide on how to uninstall autoconf-archive on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                autoconf-archive
            
                    
    
    Copied

3. Information about the autoconf-archive package on openSUSE Leap

Information for package autoconf-archive:
-----------------------------------------
Repository : Main Repository
Name : autoconf-archive
Version : 2017.09.28-1.18
Arch : noarch
Vendor : SUSE LLC
Installed Size : 2.2 MiB
Installed : No
Status : not installed
Source package : autoconf-archive-2017.09.28-1.18.src
Upstream URL : https://savannah.gnu.org/projects/autoconf-archive
Summary : A Collection of macros for GNU autoconf
Description :
The GNU Autoconf Archive is a collection of more than 450 macros for `GNU
Autoconf `_ that have been contributed as
free software by friendly supporters of the cause from all over the Internet.
Every single one of those macros can be re-used without imposing any
restrictions whatsoever on the licensing of the generated `configure` script. In
particular, it is possible to use all those macros in `configure` scripts that
are meant for non-free software. This policy is unusual for a Free Software
Foundation project. The FSF firmly believes that software ought to be free, and
software licenses like the GPL are specifically designed to ensure that
derivative work based on free software must be free as well. In case of
Autoconf, however, an exception has been made, because Autoconf is at such a
pivotal position in the software development tool chain that the benefits from
having this tool available as widely as possible outweigh the disadvantage that
some authors may choose to use it, too, for proprietary software.