How to Install and Uninstall qca-qt5.x86_64 Package on Red Hat Enterprise Linux 9 (RHEL 9)
Last updated: November 26,2024
1. Install "qca-qt5.x86_64" package
This is a short guide on how to install qca-qt5.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9)
$
sudo dnf update
Copied
$
sudo dnf install
qca-qt5.x86_64
Copied
2. Uninstall "qca-qt5.x86_64" package
In this section, we are going to explain the necessary steps to uninstall qca-qt5.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9):
$
sudo dnf remove
qca-qt5.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the qca-qt5.x86_64 package on Red Hat Enterprise Linux 9 (RHEL 9)
Last metadata expiration check: 1:29:54 ago on Mon Feb 26 07:04:30 2024.
Available Packages
Name : qca-qt5
Version : 2.3.6
Release : 1.el9
Architecture : x86_64
Size : 456 k
Source : qca-2.3.6-1.el9.src.rpm
Repository : epel
Summary : Qt5 Cryptographic Architecture
URL : https://userbase.kde.org/QCA
License : LGPLv2+
Description : Taking a hint from the similarly-named Java Cryptography Architecture,
: QCA aims to provide a straightforward and cross-platform crypto API,
: using Qt datatypes and conventions. QCA separates the API from the
: implementation, using plugins known as Providers. The advantage of this
: model is to allow applications to avoid linking to or explicitly depending
: on any particular cryptographic library. This allows one to easily change
: or upgrade crypto implementations without even needing to recompile the
: application!
Available Packages
Name : qca-qt5
Version : 2.3.6
Release : 1.el9
Architecture : x86_64
Size : 456 k
Source : qca-2.3.6-1.el9.src.rpm
Repository : epel
Summary : Qt5 Cryptographic Architecture
URL : https://userbase.kde.org/QCA
License : LGPLv2+
Description : Taking a hint from the similarly-named Java Cryptography Architecture,
: QCA aims to provide a straightforward and cross-platform crypto API,
: using Qt datatypes and conventions. QCA separates the API from the
: implementation, using plugins known as Providers. The advantage of this
: model is to allow applications to avoid linking to or explicitly depending
: on any particular cryptographic library. This allows one to easily change
: or upgrade crypto implementations without even needing to recompile the
: application!