How to Install and Uninstall lmdb Package on openSuSE Tumbleweed
Last updated: November 23,2024
1. Install "lmdb" package
Please follow the step by step instructions below to install lmdb on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
lmdb
Copied
2. Uninstall "lmdb" package
Here is a brief guide to show you how to uninstall lmdb on openSuSE Tumbleweed:
$
sudo zypper remove
lmdb
Copied
3. Information about the lmdb package on openSuSE Tumbleweed
Information for package lmdb:
-----------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : lmdb
Version : 0.9.30-2.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 113.0 KiB
Installed : No
Status : not installed
Source package : lmdb-0.9.30-2.1.src
Upstream URL : https://symas.com/mdb/
Summary : Lightning Memory-Mapped Database Manager
Description :
LMDB is a Btree-based database management library with an API similar
to BerkeleyDB. The library is thread-aware and supports concurrent
read/write access from multiple processes and threads. The DB
structure is multi-versioned, and data pages use a copy-on-write
strategy, which also provides resistance to corruption and eliminates
the need for any recovery procedures. The database is exposed in a
memory map, requiring no page cache layer of its own.
-----------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : lmdb
Version : 0.9.30-2.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 113.0 KiB
Installed : No
Status : not installed
Source package : lmdb-0.9.30-2.1.src
Upstream URL : https://symas.com/mdb/
Summary : Lightning Memory-Mapped Database Manager
Description :
LMDB is a Btree-based database management library with an API similar
to BerkeleyDB. The library is thread-aware and supports concurrent
read/write access from multiple processes and threads. The DB
structure is multi-versioned, and data pages use a copy-on-write
strategy, which also provides resistance to corruption and eliminates
the need for any recovery procedures. The database is exposed in a
memory map, requiring no page cache layer of its own.