How to Install and Uninstall perl-URI-FromHash.noarch Package on Rocky Linux 8
Last updated: November 13,2024
1. Install "perl-URI-FromHash.noarch" package
This guide covers the steps necessary to install perl-URI-FromHash.noarch on Rocky Linux 8
$
sudo dnf update
Copied
$
sudo dnf install
perl-URI-FromHash.noarch
Copied
2. Uninstall "perl-URI-FromHash.noarch" package
Please follow the steps below to uninstall perl-URI-FromHash.noarch on Rocky Linux 8:
$
sudo dnf remove
perl-URI-FromHash.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-URI-FromHash.noarch package on Rocky Linux 8
Last metadata expiration check: 2:28:23 ago on Mon Sep 12 10:27:18 2022.
Available Packages
Name : perl-URI-FromHash
Version : 0.05
Release : 12.el8
Architecture : noarch
Size : 20 k
Source : perl-URI-FromHash-0.05-12.el8.src.rpm
Repository : epel
Summary : Build a URI from a set of named parameters
URL : https://metacpan.org/release/URI-FromHash
License : GPL+ or Artistic
Description : This module provides a simple one-subroutine "named parameters" style
: interface for creating URIs. Underneath the hood it uses 'URI.pm', though
: because of the simplified interface it may not support all possible options
: for all types of URIs.
:
: It was created for the common case where you simply want to have a simple
: interface for creating syntactically correct URIs from known components
: (like a path and query string). Doing this using the native 'URI.pm'
: interface is rather tedious, requiring a number of method calls, which is
: particularly ugly when done inside a templating system such as Mason or
: TT2.
Available Packages
Name : perl-URI-FromHash
Version : 0.05
Release : 12.el8
Architecture : noarch
Size : 20 k
Source : perl-URI-FromHash-0.05-12.el8.src.rpm
Repository : epel
Summary : Build a URI from a set of named parameters
URL : https://metacpan.org/release/URI-FromHash
License : GPL+ or Artistic
Description : This module provides a simple one-subroutine "named parameters" style
: interface for creating URIs. Underneath the hood it uses 'URI.pm', though
: because of the simplified interface it may not support all possible options
: for all types of URIs.
:
: It was created for the common case where you simply want to have a simple
: interface for creating syntactically correct URIs from known components
: (like a path and query string). Doing this using the native 'URI.pm'
: interface is rather tedious, requiring a number of method calls, which is
: particularly ugly when done inside a templating system such as Mason or
: TT2.