How to Install and Uninstall perl-Thread-Semaphore.noarch Package on Fedora 34
Last updated: January 11,2025
1. Install "perl-Thread-Semaphore.noarch" package
Please follow the guidance below to install perl-Thread-Semaphore.noarch on Fedora 34
$
sudo dnf update
Copied
$
sudo dnf install
perl-Thread-Semaphore.noarch
Copied
2. Uninstall "perl-Thread-Semaphore.noarch" package
In this section, we are going to explain the necessary steps to uninstall perl-Thread-Semaphore.noarch on Fedora 34:
$
sudo dnf remove
perl-Thread-Semaphore.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-Thread-Semaphore.noarch package on Fedora 34
Last metadata expiration check: 5:33:32 ago on Tue Sep 6 08:10:37 2022.
Available Packages
Name : perl-Thread-Semaphore
Version : 2.13
Release : 477.fc34
Architecture : noarch
Size : 26 k
Source : perl-5.32.1-477.fc34.src.rpm
Repository : updates
Summary : Thread-safe semaphores
URL : https://www.perl.org/
License : GPL+ or Artistic
Description : Semaphores provide a mechanism to regulate access to resources. Unlike locks,
: semaphores aren't tied to particular scalars, and so may be used to control
: access to anything you care to use them for. Semaphores don't limit their
: values to zero and one, so they can be used to control access to some resource
: that there may be more than one of (e.g., file handles). Increment and
: decrement amounts aren't fixed at one either, so threads can reserve or return
: multiple resources at once.
Available Packages
Name : perl-Thread-Semaphore
Version : 2.13
Release : 477.fc34
Architecture : noarch
Size : 26 k
Source : perl-5.32.1-477.fc34.src.rpm
Repository : updates
Summary : Thread-safe semaphores
URL : https://www.perl.org/
License : GPL+ or Artistic
Description : Semaphores provide a mechanism to regulate access to resources. Unlike locks,
: semaphores aren't tied to particular scalars, and so may be used to control
: access to anything you care to use them for. Semaphores don't limit their
: values to zero and one, so they can be used to control access to some resource
: that there may be more than one of (e.g., file handles). Increment and
: decrement amounts aren't fixed at one either, so threads can reserve or return
: multiple resources at once.