How to Install and Uninstall perl-Test-Refcount.noarch Package on Oracle Linux 8
Last updated: November 13,2024
1. Install "perl-Test-Refcount.noarch" package
Learn how to install perl-Test-Refcount.noarch on Oracle Linux 8
$
sudo dnf update
Copied
$
sudo dnf install
perl-Test-Refcount.noarch
Copied
2. Uninstall "perl-Test-Refcount.noarch" package
This tutorial shows how to uninstall perl-Test-Refcount.noarch on Oracle Linux 8:
$
sudo dnf remove
perl-Test-Refcount.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-Test-Refcount.noarch package on Oracle Linux 8
Last metadata expiration check: 1:30:25 ago on Mon Sep 12 02:51:38 2022.
Available Packages
Name : perl-Test-Refcount
Version : 0.10
Release : 3.el8
Architecture : noarch
Size : 28 k
Source : perl-Test-Refcount-0.10-3.el8.src.rpm
Repository : epel
Summary : Assert reference counts on objects
URL : https://metacpan.org/release/Test-Refcount
License : GPL+ or Artistic
Description : The Perl garbage collector uses simple reference counting during the normal
: execution of a program. This means that cycles or unweakened references in
: other parts of code can keep an object around for longer than intended. To
: help avoid this problem, the reference count of a new object from its class
: constructor ought to be 1. This way, the caller can know the object will be
: properly DESTROYed when it drops all of its references to it.
Available Packages
Name : perl-Test-Refcount
Version : 0.10
Release : 3.el8
Architecture : noarch
Size : 28 k
Source : perl-Test-Refcount-0.10-3.el8.src.rpm
Repository : epel
Summary : Assert reference counts on objects
URL : https://metacpan.org/release/Test-Refcount
License : GPL+ or Artistic
Description : The Perl garbage collector uses simple reference counting during the normal
: execution of a program. This means that cycles or unweakened references in
: other parts of code can keep an object around for longer than intended. To
: help avoid this problem, the reference count of a new object from its class
: constructor ought to be 1. This way, the caller can know the object will be
: properly DESTROYed when it drops all of its references to it.