How to Install and Uninstall ruby3.3-rubygem-diff-lcs Package on openSuSE Tumbleweed

Last updated: November 23,2024

1. Install "ruby3.3-rubygem-diff-lcs" package

Please follow the steps below to install ruby3.3-rubygem-diff-lcs on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                ruby3.3-rubygem-diff-lcs
            
                    
    
    Copied

2. Uninstall "ruby3.3-rubygem-diff-lcs" package

Here is a brief guide to show you how to uninstall ruby3.3-rubygem-diff-lcs on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                ruby3.3-rubygem-diff-lcs
            
                    
    
    Copied

3. Information about the ruby3.3-rubygem-diff-lcs package on openSuSE Tumbleweed

Information for package ruby3.3-rubygem-diff-lcs:
-------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : ruby3.3-rubygem-diff-lcs
Version : 1.5.0-1.14
Arch : x86_64
Vendor : openSUSE
Installed Size : 179.3 KiB
Installed : No
Status : not installed
Source package : rubygem-diff-lcs-1.5.0-1.14.src
Upstream URL : https://github.com/halostatue/diff-lcs
Summary : Diff::LCS computes the difference between two Enumerable sequences
Description :
Diff::LCS computes the difference between two Enumerable sequences using the
McIlroy-Hunt longest common subsequence (LCS) algorithm. It includes utilities
to create a simple HTML diff output format and a standard diff-like tool.
This is release 1.4.3, providing a simple extension that allows for
Diff::LCS::Change objects to be treated implicitly as arrays and fixes a
number of formatting issues.
Ruby versions below 2.5 are soft-deprecated, which means that older versions
are no longer part of the CI test suite. If any changes have been introduced
that break those versions, bug reports and patches will be accepted, but it
will be up to the reporter to verify any fixes prior to release. The next
major release will completely break compatibility.