How to Install and Uninstall libverto1 Package on openSuSE Tumbleweed
Last updated: November 05,2024
1. Install "libverto1" package
Please follow the step by step instructions below to install libverto1 on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
libverto1
Copied
2. Uninstall "libverto1" package
Learn how to uninstall libverto1 on openSuSE Tumbleweed:
$
sudo zypper remove
libverto1
Copied
3. Information about the libverto1 package on openSuSE Tumbleweed
Information for package libverto1:
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : libverto1
Version : 0.3.2-3.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 27.8 KiB
Installed : Yes (automatically)
Status : up-to-date
Source package : libverto-0.3.2-3.2.src
Upstream URL : https://github.com/latchset/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 : openSUSE-Tumbleweed-Oss
Name : libverto1
Version : 0.3.2-3.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 27.8 KiB
Installed : Yes (automatically)
Status : up-to-date
Source package : libverto-0.3.2-3.2.src
Upstream URL : https://github.com/latchset/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.