How to Install and Uninstall tntdb-doc Package on openSuSE Tumbleweed
Last updated: November 27,2024
1. Install "tntdb-doc" package
This tutorial shows how to install tntdb-doc on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
tntdb-doc
Copied
2. Uninstall "tntdb-doc" package
This guide covers the steps necessary to uninstall tntdb-doc on openSuSE Tumbleweed:
$
sudo zypper remove
tntdb-doc
Copied
3. Information about the tntdb-doc package on openSuSE Tumbleweed
Information for package tntdb-doc:
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : tntdb-doc
Version : 1.4-1.17
Arch : noarch
Vendor : openSUSE
Installed Size : 1.6 MiB
Installed : No
Status : not installed
Source package : tntdb-1.4-1.17.src
Upstream URL : http://www.tntnet.org/index.html
Summary : Documentation for tntdb
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.
This package contains documentation
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : tntdb-doc
Version : 1.4-1.17
Arch : noarch
Vendor : openSUSE
Installed Size : 1.6 MiB
Installed : No
Status : not installed
Source package : tntdb-1.4-1.17.src
Upstream URL : http://www.tntnet.org/index.html
Summary : Documentation for tntdb
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.
This package contains documentation