How to Install and Uninstall perl-Devel-GlobalDestruction.noarch Package on Fedora 34
Last updated: November 30,2024
1. Install "perl-Devel-GlobalDestruction.noarch" package
In this section, we are going to explain the necessary steps to install perl-Devel-GlobalDestruction.noarch on Fedora 34
$
sudo dnf update
Copied
$
sudo dnf install
perl-Devel-GlobalDestruction.noarch
Copied
2. Uninstall "perl-Devel-GlobalDestruction.noarch" package
In this section, we are going to explain the necessary steps to uninstall perl-Devel-GlobalDestruction.noarch on Fedora 34:
$
sudo dnf remove
perl-Devel-GlobalDestruction.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-Devel-GlobalDestruction.noarch package on Fedora 34
Last metadata expiration check: 4:56:06 ago on Tue Sep 6 02:10:55 2022.
Available Packages
Name : perl-Devel-GlobalDestruction
Version : 0.14
Release : 14.fc34
Architecture : noarch
Size : 17 k
Source : perl-Devel-GlobalDestruction-0.14-14.fc34.src.rpm
Repository : fedora
Summary : Expose PL_dirty, the flag that marks global destruction
URL : https://metacpan.org/release/Devel-GlobalDestruction
License : GPL+ or Artistic
Description : Perl's global destruction is a little tricky to deal with with respect to
: finalizers because it's not ordered and objects can sometimes disappear.
:
: Writing defensive destructors is hard and annoying, and usually if global
: destruction is happening you only need the destructors that free up non
: process local resources to actually execute.
:
: For these constructors you can avoid the mess by simply bailing out if
: global destruction is in effect.
Available Packages
Name : perl-Devel-GlobalDestruction
Version : 0.14
Release : 14.fc34
Architecture : noarch
Size : 17 k
Source : perl-Devel-GlobalDestruction-0.14-14.fc34.src.rpm
Repository : fedora
Summary : Expose PL_dirty, the flag that marks global destruction
URL : https://metacpan.org/release/Devel-GlobalDestruction
License : GPL+ or Artistic
Description : Perl's global destruction is a little tricky to deal with with respect to
: finalizers because it's not ordered and objects can sometimes disappear.
:
: Writing defensive destructors is hard and annoying, and usually if global
: destruction is happening you only need the destructors that free up non
: process local resources to actually execute.
:
: For these constructors you can avoid the mess by simply bailing out if
: global destruction is in effect.