How to Install and Uninstall perl-DBD-Mock.noarch Package on Rocky Linux 8
Last updated: September 06,2024
1. Install "perl-DBD-Mock.noarch" package
This guide covers the steps necessary to install perl-DBD-Mock.noarch on Rocky Linux 8
$
sudo dnf update
Copied
$
sudo dnf install
perl-DBD-Mock.noarch
Copied
2. Uninstall "perl-DBD-Mock.noarch" package
This tutorial shows how to uninstall perl-DBD-Mock.noarch on Rocky Linux 8:
$
sudo dnf remove
perl-DBD-Mock.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-DBD-Mock.noarch package on Rocky Linux 8
Last metadata expiration check: 0:19:11 ago on Mon Sep 12 10:27:18 2022.
Available Packages
Name : perl-DBD-Mock
Version : 1.55
Release : 2.el8
Architecture : noarch
Size : 71 k
Source : perl-DBD-Mock-1.55-2.el8.src.rpm
Repository : epel
Summary : Mock database driver for testing
URL : https://metacpan.org/release/DBD-Mock
License : GPL+ or Artistic
Description : Testing with databases can be tricky. If you are developing a system married
: to a single database then you can make some assumptions about your environment
: and ask the user to provide relevant connection information. But if you need
: to test a framework that uses DBI, particularly a framework that uses
: different types of persistence schemes, then it may be more useful to simply
: verify what the framework is trying to do -- ensure the right SQL is generated
: and that the correct parameters are bound. DBD::Mock makes it easy to just
: modify your configuration (presumably held outside your code) and just use it
: instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework.
Available Packages
Name : perl-DBD-Mock
Version : 1.55
Release : 2.el8
Architecture : noarch
Size : 71 k
Source : perl-DBD-Mock-1.55-2.el8.src.rpm
Repository : epel
Summary : Mock database driver for testing
URL : https://metacpan.org/release/DBD-Mock
License : GPL+ or Artistic
Description : Testing with databases can be tricky. If you are developing a system married
: to a single database then you can make some assumptions about your environment
: and ask the user to provide relevant connection information. But if you need
: to test a framework that uses DBI, particularly a framework that uses
: different types of persistence schemes, then it may be more useful to simply
: verify what the framework is trying to do -- ensure the right SQL is generated
: and that the correct parameters are bound. DBD::Mock makes it easy to just
: modify your configuration (presumably held outside your code) and just use it
: instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework.