How to Install and Uninstall perl-Config-GitLike Package on openSUSE Leap

Information for package perl-Config-GitLike:
--------------------------------------------
Repository : Main Repository
Name : perl-Config-GitLike
Version : 1.18-bp155.2.8
Arch : noarch
Vendor : openSUSE
Installed Size : 80.8 KiB
Installed : No
Status : not installed
Source package : perl-Config-GitLike-1.18-bp155.2.8.src
Upstream URL : https://metacpan.org/release/Config-GitLike
Summary : Git-compatible config file parsing
Description :
This module handles interaction with configuration files of the style used
by the version control system Git. It can both parse and modify these
files, as well as create entirely new ones.
You only need to know a few things about the configuration format in order
to use this module. First, a configuration file is made up of key/value
pairs. Every key must be contained in a section. Sections can have
subsections, but they don't have to. For the purposes of setting and
getting configuration variables, we join the section name, subsection name,
and variable name together with dots to get a key name that looks like
"section.subsection.variable". These are the strings that you'll be passing
in to 'key' arguments.
Configuration files inherit from each other. By default, 'Config::GitLike'
loads data from a system-wide configuration file, a per-user configuration
file, and a per-directory configuration file, but by subclassing and
overriding methods you can obtain any combination of configuration files.
By default, configuration files that don't exist are just skipped.
See
http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_configurat
ion_file for details on the syntax of git configuration files. We won't
waste pixels on the nitty gritty here.
While the behavior of a couple of this module's methods differ slightly
from the 'git config' equivalents, this module can read any config file
written by git. The converse is usually true, but only if you don't take
advantage of this module's increased permissiveness when it comes to key
names. (See DIFFERENCES FROM GIT-CONFIG for details.)
This is an object-oriented module using Moo. All subroutines are object
method calls.
A few methods have parameters that are always used for the same purpose: