How to Install and Uninstall perl-Devel-GlobalDestruction Package on openSUSE Leap
Last updated: December 24,2024
1. Install "perl-Devel-GlobalDestruction" package
Please follow the instructions below to install perl-Devel-GlobalDestruction on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
perl-Devel-GlobalDestruction
Copied
2. Uninstall "perl-Devel-GlobalDestruction" package
This guide covers the steps necessary to uninstall perl-Devel-GlobalDestruction on openSUSE Leap:
$
sudo zypper remove
perl-Devel-GlobalDestruction
Copied
3. Information about the perl-Devel-GlobalDestruction package on openSUSE Leap
Information for package perl-Devel-GlobalDestruction:
-----------------------------------------------------
Repository : Main Repository
Name : perl-Devel-GlobalDestruction
Version : 0.14-bp155.2.12
Arch : noarch
Vendor : openSUSE
Installed Size : 8.4 KiB
Installed : No
Status : not installed
Source package : perl-Devel-GlobalDestruction-0.14-bp155.2.12.src
Upstream URL : http://search.cpan.org/dist/Devel-GlobalDestruction/
Summary : Provides function returning the equivalent of
Description :
Perl's global destruction is a little tricky to deal with WRT 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.
-----------------------------------------------------
Repository : Main Repository
Name : perl-Devel-GlobalDestruction
Version : 0.14-bp155.2.12
Arch : noarch
Vendor : openSUSE
Installed Size : 8.4 KiB
Installed : No
Status : not installed
Source package : perl-Devel-GlobalDestruction-0.14-bp155.2.12.src
Upstream URL : http://search.cpan.org/dist/Devel-GlobalDestruction/
Summary : Provides function returning the equivalent of
Description :
Perl's global destruction is a little tricky to deal with WRT 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.