How to Install and Uninstall libtntdb5 Package on openSUSE Leap
Last updated: December 28,2024
1. Install "libtntdb5" package
Please follow the guidance below to install libtntdb5 on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
libtntdb5
Copied
2. Uninstall "libtntdb5" package
This guide covers the steps necessary to uninstall libtntdb5 on openSUSE Leap:
$
sudo zypper remove
libtntdb5
Copied
3. Information about the libtntdb5 package on openSUSE Leap
Information for package libtntdb5:
----------------------------------
Repository : Main Repository
Name : libtntdb5
Version : 1.4-bp155.2.12
Arch : x86_64
Vendor : openSUSE
Installed Size : 301.9 KiB
Installed : No
Status : not installed
Source package : tntdb-1.4-bp155.2.12.src
Upstream URL : http://www.tntnet.org/index.html
Summary : Library for simple database access
Description :
Tntdb is a library for simple database access.
The database independent layer offers easy to use methods for working with the database and also greatly simplifies resource-management. The classes hold reference-counted pointers to the actual implementation. They are copyable and assignable. The user can use the classes just like simple values. The resources they reference are freed, when the last reference is deleted. This happens normally just by leaving the scope. There is normally no reason to instantiate them dynamically on the heap.
The driver-layer contains the actual implementation, which does the work. These classes are database-dependent. The user normally doesn't need to deal with this.
----------------------------------
Repository : Main Repository
Name : libtntdb5
Version : 1.4-bp155.2.12
Arch : x86_64
Vendor : openSUSE
Installed Size : 301.9 KiB
Installed : No
Status : not installed
Source package : tntdb-1.4-bp155.2.12.src
Upstream URL : http://www.tntnet.org/index.html
Summary : Library for simple database access
Description :
Tntdb is a library for simple database access.
The database independent layer offers easy to use methods for working with the database and also greatly simplifies resource-management. The classes hold reference-counted pointers to the actual implementation. They are copyable and assignable. The user can use the classes just like simple values. The resources they reference are freed, when the last reference is deleted. This happens normally just by leaving the scope. There is normally no reason to instantiate them dynamically on the heap.
The driver-layer contains the actual implementation, which does the work. These classes are database-dependent. The user normally doesn't need to deal with this.