How to Install and Uninstall libslz.x86_64 Package on Fedora 35

Last updated: October 06,2024

1. Install "libslz.x86_64" package

Please follow the guidelines below to install libslz.x86_64 on Fedora 35


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                libslz.x86_64
            
                    
    
    Copied

2. Uninstall "libslz.x86_64" package

Please follow the step by step instructions below to uninstall libslz.x86_64 on Fedora 35:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                libslz.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the libslz.x86_64 package on Fedora 35

Last metadata expiration check: 0:19:00 ago on Wed Sep 7 14:25:02 2022.
Available Packages
Name : libslz
Version : 1.2.0
Release : 4.fc35
Architecture : x86_64
Size : 53 k
Source : libslz-1.2.0-4.fc35.src.rpm
Repository : fedora
Summary : StateLess Zip
URL : http://www.libslz.org/
License : MIT
Description : SLZ is a fast and memory-less stream compressor which produces an output that
: can be decompressed with zlib or gzip. It does not implement decompression at
: all, zlib is perfectly fine for this.
:
: The purpose is to use SLZ in situations where a zlib-compatible stream is
: needed and zlib's resource usage would be too high while the compression ratio
: is not critical. The typical use case is in HTTP servers and gateways which
: have to compress many streams in parallel with little CPU resources to assign
: to this task, and without having to limit the compression ratio due to the
: memory usage. In such an environment, the server's memory usage can easily be
: divided by 10 and the CPU usage by 3.