How to Install and Uninstall perl-JSON Package on openSuSE Tumbleweed

Last updated: May 18,2024

1. Install "perl-JSON" package

This is a short guide on how to install perl-JSON on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                perl-JSON
            
                    
    
    Copied

2. Uninstall "perl-JSON" package

This guide covers the steps necessary to uninstall perl-JSON on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                perl-JSON
            
                    
    
    Copied

3. Information about the perl-JSON package on openSuSE Tumbleweed

Information for package perl-JSON:
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-JSON
Version : 4.10-1.5
Arch : noarch
Vendor : openSUSE
Installed Size : 270.3 KiB
Installed : No
Status : not installed
Source package : perl-JSON-4.10-1.5.src
Upstream URL : https://metacpan.org/release/JSON
Summary : JSON (JavaScript Object Notation) encoder/decoder
Description :
This module is a thin wrapper for JSON::XS-compatible modules with a few
additional features. All the backend modules convert a Perl data structure
to a JSON text and vice versa. This module uses JSON::XS by default, and
when JSON::XS is not available, falls back on JSON::PP, which is in the
Perl core since 5.14. If JSON::PP is not available either, this module then
falls back on JSON::backportPP (which is actually JSON::PP in a different
.pm file) bundled in the same distribution as this module. You can also
explicitly specify to use Cpanel::JSON::XS, a fork of JSON::XS by Reini
Urban.
All these backend modules have slight incompatibilities between them,
including extra features that other modules don't support, but as long as
you use only common features (most important ones are described below),
migration from backend to backend should be reasonably easy. For details,
see each backend module you use.