How to Install and Uninstall libverto1-32bit Package on openSUSE Leap
Last updated: December 26,2024
1. Install "libverto1-32bit" package
This is a short guide on how to install libverto1-32bit on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
libverto1-32bit
Copied
2. Uninstall "libverto1-32bit" package
In this section, we are going to explain the necessary steps to uninstall libverto1-32bit on openSUSE Leap:
$
sudo zypper remove
libverto1-32bit
Copied
3. Information about the libverto1-32bit package on openSUSE Leap
Information for package libverto1-32bit:
----------------------------------------
Repository : Main Repository
Name : libverto1-32bit
Version : 0.2.6-3.20
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 17.4 KiB
Installed : No
Status : not installed
Source package : libverto-0.2.6-3.20.src
Upstream URL : https://fedorahosted.org/libverto
Summary : Runtime libraries for libverto
Description :
libverto provides a way for libraries to expose asynchronous
interfaces without having to choose a particular event loop,
offloading this decision to the end application which consumes the
library.
If you are packaging an application, not library, based on libverto,
you should depend either on a specific implementation module or you
can depend on the virtual provides 'libverto-module-base'. This will
ensure that you have at least one module installed that provides io,
timeout and signal functionality. Currently glib is the only module
that does not provide these three because it lacks signal. However,
glib will support signal in the future.
----------------------------------------
Repository : Main Repository
Name : libverto1-32bit
Version : 0.2.6-3.20
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 17.4 KiB
Installed : No
Status : not installed
Source package : libverto-0.2.6-3.20.src
Upstream URL : https://fedorahosted.org/libverto
Summary : Runtime libraries for libverto
Description :
libverto provides a way for libraries to expose asynchronous
interfaces without having to choose a particular event loop,
offloading this decision to the end application which consumes the
library.
If you are packaging an application, not library, based on libverto,
you should depend either on a specific implementation module or you
can depend on the virtual provides 'libverto-module-base'. This will
ensure that you have at least one module installed that provides io,
timeout and signal functionality. Currently glib is the only module
that does not provide these three because it lacks signal. However,
glib will support signal in the future.