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

Last updated: May 14,2024

1. Install "ruby3.3-rubygem-debug_inspector" package

Here is a brief guide to show you how to install ruby3.3-rubygem-debug_inspector on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                ruby3.3-rubygem-debug_inspector
            
                    
    
    Copied

2. Uninstall "ruby3.3-rubygem-debug_inspector" package

This guide covers the steps necessary to uninstall ruby3.3-rubygem-debug_inspector on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                ruby3.3-rubygem-debug_inspector
            
                    
    
    Copied

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

Information for package ruby3.3-rubygem-debug_inspector:
--------------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : ruby3.3-rubygem-debug_inspector
Version : 1.2.0-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 37.6 KiB
Installed : No
Status : not installed
Source package : rubygem-debug_inspector-1.2.0-1.1.src
Upstream URL : https://github.com/banister/debug_inspector
Summary : A Ruby wrapper for the MRI 2.0 debug_inspector API
Description :
Adds methods to DebugInspector to allow for inspection of backtrace frames.
The debug_inspector C extension and API were designed and built by Koichi
Sasada, this project is just a gemification of his work.
This library makes use of the debug inspector API which was added to MRI
2.0.0.
Only works on MRI 2 and 3. Requiring it on unsupported Rubies will result in a
no-op.
Recommended for use only in debugging situations. Do not use this in
production apps.