How to Install and Uninstall python2-plaster Package on openSUSE Leap
Last updated: December 25,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "python2-plaster" package
This guide let you learn how to install python2-plaster on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
python2-plaster
Copied
2. Uninstall "python2-plaster" package
Please follow the guidelines below to uninstall python2-plaster on openSUSE Leap:
$
sudo zypper remove
python2-plaster
Copied
3. Information about the python2-plaster package on openSUSE Leap
Information for package python2-plaster:
----------------------------------------
Repository : Main Repository
Name : python2-plaster
Version : 1.0-bp153.1.15
Arch : noarch
Vendor : openSUSE
Installed Size : 34,0 KiB
Installed : No
Status : not installed
Source package : python-plaster-1.0-bp153.1.15.src
Summary : A loader interface around multiple config file formats
Description :
Plaster is a loader interface around multiple config file formats.
It exists to define a common API for applications to use when they
wish to load a configuration. The library itself does not aim to
handle anything except a basic API that applications may use to find
and load configuration settings. Any specific constraints should be
implemented in a pluggable loader which can be registered via an
entrypoint.
----------------------------------------
Repository : Main Repository
Name : python2-plaster
Version : 1.0-bp153.1.15
Arch : noarch
Vendor : openSUSE
Installed Size : 34,0 KiB
Installed : No
Status : not installed
Source package : python-plaster-1.0-bp153.1.15.src
Summary : A loader interface around multiple config file formats
Description :
Plaster is a loader interface around multiple config file formats.
It exists to define a common API for applications to use when they
wish to load a configuration. The library itself does not aim to
handle anything except a basic API that applications may use to find
and load configuration settings. Any specific constraints should be
implemented in a pluggable loader which can be registered via an
entrypoint.