How to Install and Uninstall python3-plaster.noarch Package on CentOS 8 / RHEL 8
Last updated: November 01,2024
1. Install "python3-plaster.noarch" package
Please follow the guidance below to install python3-plaster.noarch on CentOS 8 / RHEL 8
$
sudo dnf update
Copied
$
sudo dnf install
python3-plaster.noarch
Copied
2. Uninstall "python3-plaster.noarch" package
This guide covers the steps necessary to uninstall python3-plaster.noarch on CentOS 8 / RHEL 8:
$
sudo dnf remove
python3-plaster.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the python3-plaster.noarch package on CentOS 8 / RHEL 8
Last metadata expiration check: 1 day, 7:59:52 ago on Sun May 9 13:03:46 2021.
Available Packages
Name : python3-plaster
Version : 0.5
Release : 6.el8
Architecture : noarch
Size : 25 k
Source : python-plaster-0.5-6.el8.src.rpm
Repository : epel
Summary : Application configuration settings abstraction layer
URL : https://github.com/Pylons/plaster
License : MIT
Description : plaster is a loader interface around multiple
: configuration file formats. It exists to define a common API for
: applications to use when they wish to load 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 loader which can be
: registered via an entry point.
Available Packages
Name : python3-plaster
Version : 0.5
Release : 6.el8
Architecture : noarch
Size : 25 k
Source : python-plaster-0.5-6.el8.src.rpm
Repository : epel
Summary : Application configuration settings abstraction layer
URL : https://github.com/Pylons/plaster
License : MIT
Description : plaster is a loader interface around multiple
: configuration file formats. It exists to define a common API for
: applications to use when they wish to load 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 loader which can be
: registered via an entry point.