How to Install and Uninstall perl-AnyEvent Package on openSuSE Tumbleweed
Last updated: December 23,2024
1. Install "perl-AnyEvent" package
In this section, we are going to explain the necessary steps to install perl-AnyEvent on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
perl-AnyEvent
Copied
2. Uninstall "perl-AnyEvent" package
This guide covers the steps necessary to uninstall perl-AnyEvent on openSuSE Tumbleweed:
$
sudo zypper remove
perl-AnyEvent
Copied
3. Information about the perl-AnyEvent package on openSuSE Tumbleweed
Information for package perl-AnyEvent:
--------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-AnyEvent
Version : 7.17-1.20
Arch : x86_64
Vendor : openSUSE
Installed Size : 980.7 KiB
Installed : No
Status : not installed
Source package : perl-AnyEvent-7.17-1.20.src
Upstream URL : https://metacpan.org/release/AnyEvent
Summary : The DBI of event loop programming
Description :
AnyEvent provides a uniform interface to various event loops. This allows
module authors to use event loop functionality without forcing module users
to use a specific event loop implementation (since more than one event loop
cannot coexist peacefully).
The interface itself is vaguely similar, but not identical to the Event
module.
During the first call of any watcher-creation method, the module tries to
detect the currently loaded event loop by probing whether one of the
following modules is already loaded: EV, AnyEvent::Loop, Event, Glib, Tk,
Event::Lib, Qt, POE. The first one found is used. If none are detected, the
module tries to load the first four modules in the order given; but note
that if EV is not available, the pure-perl AnyEvent::Loop should always
work, so the other two are not normally tried.
Because AnyEvent first checks for modules that are already loaded, loading
an event model explicitly before first using AnyEvent will likely make that
model the default. For example:
use Tk;
use AnyEvent;
The _likely_ means that, if any module loads another event model and starts
using it, all bets are off - this case should be very rare though, as very
few modules hardcode event loops without announcing this very loudly.
The pure-perl implementation of AnyEvent is called 'AnyEvent::Loop'. Like
other event modules you can load it explicitly and enjoy the high
availability of that event loop :)
--------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-AnyEvent
Version : 7.17-1.20
Arch : x86_64
Vendor : openSUSE
Installed Size : 980.7 KiB
Installed : No
Status : not installed
Source package : perl-AnyEvent-7.17-1.20.src
Upstream URL : https://metacpan.org/release/AnyEvent
Summary : The DBI of event loop programming
Description :
AnyEvent provides a uniform interface to various event loops. This allows
module authors to use event loop functionality without forcing module users
to use a specific event loop implementation (since more than one event loop
cannot coexist peacefully).
The interface itself is vaguely similar, but not identical to the Event
module.
During the first call of any watcher-creation method, the module tries to
detect the currently loaded event loop by probing whether one of the
following modules is already loaded: EV, AnyEvent::Loop, Event, Glib, Tk,
Event::Lib, Qt, POE. The first one found is used. If none are detected, the
module tries to load the first four modules in the order given; but note
that if EV is not available, the pure-perl AnyEvent::Loop should always
work, so the other two are not normally tried.
Because AnyEvent first checks for modules that are already loaded, loading
an event model explicitly before first using AnyEvent will likely make that
model the default. For example:
use Tk;
use AnyEvent;
The _likely_ means that, if any module loads another event model and starts
using it, all bets are off - this case should be very rare though, as very
few modules hardcode event loops without announcing this very loudly.
The pure-perl implementation of AnyEvent is called 'AnyEvent::Loop'. Like
other event modules you can load it explicitly and enjoy the high
availability of that event loop :)