How to Install and Uninstall python312-click-plugins Package on openSuSE Tumbleweed
Last updated: November 12,2024
1. Install "python312-click-plugins" package
This tutorial shows how to install python312-click-plugins on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python312-click-plugins
Copied
2. Uninstall "python312-click-plugins" package
Learn how to uninstall python312-click-plugins on openSuSE Tumbleweed:
$
sudo zypper remove
python312-click-plugins
Copied
3. Information about the python312-click-plugins package on openSuSE Tumbleweed
Information for package python312-click-plugins:
------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-click-plugins
Version : 1.1.1-5.6
Arch : noarch
Vendor : openSUSE
Installed Size : 25.4 KiB
Installed : No
Status : not installed
Source package : python-click-plugins-1.1.1-5.6.src
Upstream URL : https://github.com/click-contrib/click-plugins
Summary : Click extension to register CLI commands via setuptools entry-points
Description :
Use a decorator to get setuptools entry points that allows others
to use your commandline utility as a home for their related sub-commands.
You get to choose where these sub-commands or sub-groups can be registered
but the plugin developer gets to choose they ARE registered.
You could have all plugins register alongside the core commands,
in a special sub-group, across multiple sub-groups, or some combination.
------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-click-plugins
Version : 1.1.1-5.6
Arch : noarch
Vendor : openSUSE
Installed Size : 25.4 KiB
Installed : No
Status : not installed
Source package : python-click-plugins-1.1.1-5.6.src
Upstream URL : https://github.com/click-contrib/click-plugins
Summary : Click extension to register CLI commands via setuptools entry-points
Description :
Use a decorator to get setuptools entry points that allows others
to use your commandline utility as a home for their related sub-commands.
You get to choose where these sub-commands or sub-groups can be registered
but the plugin developer gets to choose they ARE registered.
You could have all plugins register alongside the core commands,
in a special sub-group, across multiple sub-groups, or some combination.