How to Install and Uninstall perl-autovivification.x86_64 Package on Rocky Linux 8
Last updated: November 13,2024
1. Install "perl-autovivification.x86_64" package
This tutorial shows how to install perl-autovivification.x86_64 on Rocky Linux 8
$
sudo dnf update
Copied
$
sudo dnf install
perl-autovivification.x86_64
Copied
2. Uninstall "perl-autovivification.x86_64" package
Please follow the step by step instructions below to uninstall perl-autovivification.x86_64 on Rocky Linux 8:
$
sudo dnf remove
perl-autovivification.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-autovivification.x86_64 package on Rocky Linux 8
Last metadata expiration check: 0:40:24 ago on Mon Sep 12 10:27:18 2022.
Available Packages
Name : perl-autovivification
Version : 0.18
Release : 8.el8
Architecture : x86_64
Size : 35 k
Source : perl-autovivification-0.18-8.el8.src.rpm
Repository : epel
Summary : Lexically disable autovivification
URL : https://metacpan.org/release/autovivification
License : GPL+ or Artistic
Description : When an undefined variable is dereferenced, it gets silently upgraded to an
: array or hash reference (depending of the type of the dereferencing). This
: behavior is called autovivification and usually does what you mean (e.g.
: when you store a value) but it's sometimes unnatural or surprising because
: your variables gets populated behind your back. This is especially true
: when several levels of dereferencing are involved, in which case all levels
: are vivified up to the last, or when it happens in intuitively read-only
: constructs like exists.
Available Packages
Name : perl-autovivification
Version : 0.18
Release : 8.el8
Architecture : x86_64
Size : 35 k
Source : perl-autovivification-0.18-8.el8.src.rpm
Repository : epel
Summary : Lexically disable autovivification
URL : https://metacpan.org/release/autovivification
License : GPL+ or Artistic
Description : When an undefined variable is dereferenced, it gets silently upgraded to an
: array or hash reference (depending of the type of the dereferencing). This
: behavior is called autovivification and usually does what you mean (e.g.
: when you store a value) but it's sometimes unnatural or surprising because
: your variables gets populated behind your back. This is especially true
: when several levels of dereferencing are involved, in which case all levels
: are vivified up to the last, or when it happens in intuitively read-only
: constructs like exists.