How to Install and Uninstall nss-softokn-freebl-devel.i686 Package on Rocky Linux 9
Last updated: November 15,2024
1. Install "nss-softokn-freebl-devel.i686" package
In this section, we are going to explain the necessary steps to install nss-softokn-freebl-devel.i686 on Rocky Linux 9
$
sudo dnf update
Copied
$
sudo dnf install
nss-softokn-freebl-devel.i686
Copied
2. Uninstall "nss-softokn-freebl-devel.i686" package
In this section, we are going to explain the necessary steps to uninstall nss-softokn-freebl-devel.i686 on Rocky Linux 9:
$
sudo dnf remove
nss-softokn-freebl-devel.i686
Copied
$
sudo dnf autoremove
Copied
3. Information about the nss-softokn-freebl-devel.i686 package on Rocky Linux 9
Last metadata expiration check: 0:32:25 ago on Fri Feb 16 06:49:52 2024.
Available Packages
Name : nss-softokn-freebl-devel
Version : 3.90.0
Release : 6.el9_3
Architecture : i686
Size : 61 k
Source : nss-3.90.0-6.el9_3.src.rpm
Repository : appstream
Summary : Header and Library files for doing development with the Freebl library for NSS
URL : http://www.mozilla.org/projects/security/pki/nss/
License : MPLv2.0
Description : NSS Softoken Cryptographic Module Freebl Library Development Tools
: This package supports special needs of some PKCS #11 module developers and
: is otherwise considered private to NSS. As such, the programming interfaces
: may change and the usual NSS binary compatibility commitments do not apply.
: Developers should rely only on the officially supported NSS public API.
Available Packages
Name : nss-softokn-freebl-devel
Version : 3.90.0
Release : 6.el9_3
Architecture : i686
Size : 61 k
Source : nss-3.90.0-6.el9_3.src.rpm
Repository : appstream
Summary : Header and Library files for doing development with the Freebl library for NSS
URL : http://www.mozilla.org/projects/security/pki/nss/
License : MPLv2.0
Description : NSS Softoken Cryptographic Module Freebl Library Development Tools
: This package supports special needs of some PKCS #11 module developers and
: is otherwise considered private to NSS. As such, the programming interfaces
: may change and the usual NSS binary compatibility commitments do not apply.
: Developers should rely only on the officially supported NSS public API.