How to Install and Uninstall perl-Email-MIME-ContentType.noarch Package on Rocky Linux 9
Last updated: December 12,2024
1. Install "perl-Email-MIME-ContentType.noarch" package
Please follow the guidelines below to install perl-Email-MIME-ContentType.noarch on Rocky Linux 9
$
sudo dnf update
Copied
$
sudo dnf install
perl-Email-MIME-ContentType.noarch
Copied
2. Uninstall "perl-Email-MIME-ContentType.noarch" package
Here is a brief guide to show you how to uninstall perl-Email-MIME-ContentType.noarch on Rocky Linux 9:
$
sudo dnf remove
perl-Email-MIME-ContentType.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-Email-MIME-ContentType.noarch package on Rocky Linux 9
Last metadata expiration check: 2:30:49 ago on Fri Feb 16 06:49:52 2024.
Available Packages
Name : perl-Email-MIME-ContentType
Version : 1.026
Release : 4.el9
Architecture : noarch
Size : 25 k
Source : perl-Email-MIME-ContentType-1.026-4.el9.src.rpm
Repository : epel
Summary : Parse a MIME Content-Type Header
URL : https://metacpan.org/release/Email-MIME-ContentType
License : GPL+ or Artistic
Description : This module is responsible for parsing email content type headers according
: to section 5.1 of RFC 2045. It returns a hash with entries for the type, the
: subtype, and a hash of attributes.
:
: For backward compatibility with a really unfortunate misunderstanding of RFC
: 2045 by the early implementors of this module, 'discrete' and 'composite' are
: also present in the returned hashref, with the values of 'type' and 'subtype'
: respectively.
Available Packages
Name : perl-Email-MIME-ContentType
Version : 1.026
Release : 4.el9
Architecture : noarch
Size : 25 k
Source : perl-Email-MIME-ContentType-1.026-4.el9.src.rpm
Repository : epel
Summary : Parse a MIME Content-Type Header
URL : https://metacpan.org/release/Email-MIME-ContentType
License : GPL+ or Artistic
Description : This module is responsible for parsing email content type headers according
: to section 5.1 of RFC 2045. It returns a hash with entries for the type, the
: subtype, and a hash of attributes.
:
: For backward compatibility with a really unfortunate misunderstanding of RFC
: 2045 by the early implementors of this module, 'discrete' and 'composite' are
: also present in the returned hashref, with the values of 'type' and 'subtype'
: respectively.