How to Install and Uninstall python2-click-plugins Package on openSUSE Leap
Last updated: December 27,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "python2-click-plugins" package
Here is a brief guide to show you how to install python2-click-plugins on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
python2-click-plugins
Copied
2. Uninstall "python2-click-plugins" package
Please follow the step by step instructions below to uninstall python2-click-plugins on openSUSE Leap:
$
sudo zypper remove
python2-click-plugins
Copied
3. Information about the python2-click-plugins package on openSUSE Leap
Information for package python2-click-plugins:
----------------------------------------------
Repository : Main Repository
Name : python2-click-plugins
Version : 1.1.1-bp153.1.21
Arch : noarch
Vendor : openSUSE
Installed Size : 31,7 KiB
Installed : No
Status : not installed
Source package : python-click-plugins-1.1.1-bp153.1.21.src
Summary : An extension for click 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 : Main Repository
Name : python2-click-plugins
Version : 1.1.1-bp153.1.21
Arch : noarch
Vendor : openSUSE
Installed Size : 31,7 KiB
Installed : No
Status : not installed
Source package : python-click-plugins-1.1.1-bp153.1.21.src
Summary : An extension for click 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.