How to Install and Uninstall perl-POE Package on openSUSE Leap

Last updated: November 23,2024

1. Install "perl-POE" package

Please follow the instructions below to install perl-POE on openSUSE Leap

$ sudo zypper refresh $ sudo zypper install perl-POE

2. Uninstall "perl-POE" package

This guide let you learn how to uninstall perl-POE on openSUSE Leap:

$ sudo zypper remove perl-POE

3. Information about the perl-POE package on openSUSE Leap

Information for package perl-POE:
---------------------------------
Repository : Main Repository
Name : perl-POE
Version : 1.370-bp155.1.5
Arch : noarch
Vendor : openSUSE
Installed Size : 1.3 MiB
Installed : No
Status : not installed
Source package : perl-POE-1.370-bp155.1.5.src
Upstream URL : https://metacpan.org/release/POE
Summary : Portable, event-loop agnostic eventy networking and multitasking
Description :
POE is a framework for cooperative, event driven multitasking and
networking in Perl. Other languages have similar frameworks. Python has
Twisted. TCL has "the event loop".
POE provides a unified interface for several other event loops, including
select(), IO::Poll, Glib, Gtk, Tk, Wx, and Gtk2. Many of these event loop
interfaces were written by others, with the help of POE::Test::Loops. They
may be found on the CPAN.
POE achieves its high degree of portability to different operating systems
and Perl versions by being written entirely in Perl. CPAN hosts optional XS
modules for POE if speed is more desirable than portability.
POE is designed in layers. Each layer builds atop the lower level ones.
Programs are free to use POE at any level of abstraction, and different
levels can be mixed and matched seamlessly within a single program.
Remember, though, that higher-level abstractions often require more
resources than lower-level ones. The conveniences they provide are not
free.
POE's bundled abstraction layers are the tip of a growing iceberg.
Sprocket, POE::Stage, and other CPAN distributions build upon this work.
You're encouraged to look around.
No matter how high you go, though, it all boils down to calls to
POE::Kernel. So your down-to-earth code can easily cooperate with
stratospheric systems.