How to Install and Uninstall ruby3.2-rubygem-inifile Package on openSuSE Tumbleweed

Last updated: November 16,2024

1. Install "ruby3.2-rubygem-inifile" package

Please follow the step by step instructions below to install ruby3.2-rubygem-inifile on openSuSE Tumbleweed

$ sudo zypper refresh $ sudo zypper install ruby3.2-rubygem-inifile

2. Uninstall "ruby3.2-rubygem-inifile" package

This tutorial shows how to uninstall ruby3.2-rubygem-inifile on openSuSE Tumbleweed:

$ sudo zypper remove ruby3.2-rubygem-inifile

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

Information for package ruby3.2-rubygem-inifile:
------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : ruby3.2-rubygem-inifile
Version : 3.0.0-1.35
Arch : x86_64
Vendor : openSUSE
Installed Size : 47.1 KiB
Installed : No
Status : not installed
Source package : rubygem-inifile-3.0.0-1.35.src
Upstream URL : http://rubygems.org/gems/inifile
Summary : INI file reader and writer
Description :
Although made popular by Windows, INI files can be used on any system thanks
to their flexibility. They allow a program to store configuration data, which
can then be easily parsed and changed. Two notable systems that use the INI
format are Samba and Trac.
More information about INI files can be found on the [Wikipedia
Page](http://en.wikipedia.org/wiki/INI_file).
The basic element contained in an INI file is the property. Every property has
a name and a value, delimited by an equals sign *=*. The name appears to the
left of the equals sign and the value to the right.
name=value
Section declarations start with *[* and end with *]* as in `[section1]` and
`[section2]` shown in the example below. The section declaration marks the
beginning of a section. All properties after the section declaration will be
associated with that section.
All lines beginning with a semicolon *;* or a number sign *#* are considered
to be comments. Comment lines are ignored when parsing INI files.
A typical INI file might look like this:
[section1]
; some comment on section1
var1 = foo
var2 = doodle
var3 = multiline values \
are also possible
[section2]
var1 = baz
var2 = shoodle.