How to Install and Uninstall heatshrink Package on openSuSE Tumbleweed
Last updated: November 14,2024
1. Install "heatshrink" package
In this section, we are going to explain the necessary steps to install heatshrink on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
heatshrink
Copied
2. Uninstall "heatshrink" package
This is a short guide on how to uninstall heatshrink on openSuSE Tumbleweed:
$
sudo zypper remove
heatshrink
Copied
3. Information about the heatshrink package on openSuSE Tumbleweed
Information for package heatshrink:
-----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : heatshrink
Version : 0.4.1-1.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 14.9 KiB
Installed : No
Status : not installed
Source package : heatshrink-0.4.1-1.2.src
Upstream URL : https://github.com/atomicobject/heatshrink
Summary : Data compression library for embedded/real-time systems
Description :
A data compression/decompression library for embedded/real-time systems.
Key Features:
* Low memory usage (as low as 50 bytes) It is useful for some cases with less than 50 bytes, and useful for many general cases with < 300 bytes.
* Incremental, bounded CPU use You can chew on input data in arbitrarily tiny bites. This is a useful property in hard real-time environments.
* Can use either static or dynamic memory allocation The library doesn't impose any constraints on memory management.
* ISC license You can use it freely, even for commercial purposes.
-----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : heatshrink
Version : 0.4.1-1.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 14.9 KiB
Installed : No
Status : not installed
Source package : heatshrink-0.4.1-1.2.src
Upstream URL : https://github.com/atomicobject/heatshrink
Summary : Data compression library for embedded/real-time systems
Description :
A data compression/decompression library for embedded/real-time systems.
Key Features:
* Low memory usage (as low as 50 bytes) It is useful for some cases with less than 50 bytes, and useful for many general cases with < 300 bytes.
* Incremental, bounded CPU use You can chew on input data in arbitrarily tiny bites. This is a useful property in hard real-time environments.
* Can use either static or dynamic memory allocation The library doesn't impose any constraints on memory management.
* ISC license You can use it freely, even for commercial purposes.