How to Install and Uninstall perl-Carp.noarch Package on Rocky Linux 8
Last updated: November 14,2024
1. Install "perl-Carp.noarch" package
Please follow the instructions below to install perl-Carp.noarch on Rocky Linux 8
$
sudo dnf update
Copied
$
sudo dnf install
perl-Carp.noarch
Copied
2. Uninstall "perl-Carp.noarch" package
This is a short guide on how to uninstall perl-Carp.noarch on Rocky Linux 8:
$
sudo dnf remove
perl-Carp.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-Carp.noarch package on Rocky Linux 8
Last metadata expiration check: 0:27:48 ago on Mon Sep 12 10:27:18 2022.
Installed Packages
Name : perl-Carp
Version : 1.42
Release : 396.el8
Architecture : noarch
Size : 41 k
Source : perl-Carp-1.42-396.el8.src.rpm
Repository : @System
From repo : baseos
Summary : Alternative warn and die for modules
URL : http://search.cpan.org/dist/Carp/
License : GPL+ or Artistic
Description : The Carp routines are useful in your own modules because they act like
: die() or warn(), but with a message which is more likely to be useful to a
: user of your module. In the case of cluck, confess, and longmess that
: context is a summary of every call in the call-stack. For a shorter message
: you can use carp or croak which report the error as being from where your
: module was called. There is no guarantee that that is where the error was,
: but it is a good educated guess.
Installed Packages
Name : perl-Carp
Version : 1.42
Release : 396.el8
Architecture : noarch
Size : 41 k
Source : perl-Carp-1.42-396.el8.src.rpm
Repository : @System
From repo : baseos
Summary : Alternative warn and die for modules
URL : http://search.cpan.org/dist/Carp/
License : GPL+ or Artistic
Description : The Carp routines are useful in your own modules because they act like
: die() or warn(), but with a message which is more likely to be useful to a
: user of your module. In the case of cluck, confess, and longmess that
: context is a summary of every call in the call-stack. For a shorter message
: you can use carp or croak which report the error as being from where your
: module was called. There is no guarantee that that is where the error was,
: but it is a good educated guess.