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

Last updated: May 02,2024

1. Install "perl-TheSchwartz" package

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

$ sudo zypper refresh $ sudo zypper install perl-TheSchwartz

2. Uninstall "perl-TheSchwartz" package

In this section, we are going to explain the necessary steps to uninstall perl-TheSchwartz on openSUSE Leap:

$ sudo zypper remove perl-TheSchwartz

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

Information for package perl-TheSchwartz:
-----------------------------------------
Repository : Main Repository
Name : perl-TheSchwartz
Version : 1.17-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 121.2 KiB
Installed : No
Status : not installed
Source package : perl-TheSchwartz-1.17-bp155.1.4.src
Upstream URL : https://metacpan.org/release/TheSchwartz
Summary : Reliable job queue
Description :
TheSchwartz is a reliable job queue system. Your application can put jobs
into the system, and your worker processes can pull jobs from the queue
atomically to perform. Failed jobs can be left in the queue to retry later.
_Abilities_ specify what jobs a worker process can perform. Abilities are
the names of 'TheSchwartz::Worker' sub-classes, as in the synopsis: the
'MyWorker' class name is used to specify that the worker script can perform
the job. When using the 'TheSchwartz' client's 'work' functions, the
class-ability duality is used to automatically dispatch to the proper class
to do the actual work.
TheSchwartz clients will also prefer to do jobs for unused abilities before
reusing a particular ability, to avoid exhausting the supply of one kind of
job while jobs of other types stack up.
Some jobs with high setup times can be performed more efficiently if a
group of related jobs are performed together. TheSchwartz offers a facility
to _coalesce_ jobs into groups, which a properly constructed worker can
find and perform at once. For example, if your worker were delivering
email, you might store the domain name from the recipient's address as the
coalescing value. The worker that grabs that job could then batch deliver
all the mail for that domain once it connects to that domain's mail server.