How to Install and Uninstall perl-autovivification.x86_64 Package on Fedora 34
Last updated: October 05,2024
1. Install "perl-autovivification.x86_64" package
Please follow the steps below to install perl-autovivification.x86_64 on Fedora 34
$
sudo dnf update
Copied
$
sudo dnf install
perl-autovivification.x86_64
Copied
2. Uninstall "perl-autovivification.x86_64" package
Please follow the guidance below to uninstall perl-autovivification.x86_64 on Fedora 34:
$
sudo dnf remove
perl-autovivification.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-autovivification.x86_64 package on Fedora 34
Last metadata expiration check: 3:16:01 ago on Tue Sep 6 02:10:55 2022.
Available Packages
Name : perl-autovivification
Version : 0.18
Release : 12.fc34
Architecture : x86_64
Size : 33 k
Source : perl-autovivification-0.18-12.fc34.src.rpm
Repository : fedora
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 : 12.fc34
Architecture : x86_64
Size : 33 k
Source : perl-autovivification-0.18-12.fc34.src.rpm
Repository : fedora
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.