How to Install and Uninstall libhs5-vectorscan5 Package on openSuSE Tumbleweed
Last updated: November 24,2024
1. Install "libhs5-vectorscan5" package
Please follow the instructions below to install libhs5-vectorscan5 on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
libhs5-vectorscan5
Copied
2. Uninstall "libhs5-vectorscan5" package
This guide covers the steps necessary to uninstall libhs5-vectorscan5 on openSuSE Tumbleweed:
$
sudo zypper remove
libhs5-vectorscan5
Copied
3. Information about the libhs5-vectorscan5 package on openSuSE Tumbleweed
Information for package libhs5-vectorscan5:
-------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : libhs5-vectorscan5
Version : 5.4.10.1-1.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 13.3 MiB
Installed : No
Status : not installed
Source package : vectorscan-5.4.10.1-1.2.src
Upstream URL : https://github.com/VectorCamp/vectorscan
Summary : Regular expression matching library
Description :
A fork of Intel's Hyperscan, modified to run on more platforms.
Vectorscan will follow Intel's API and internal algorithms where possible,
but will not hesitate to make code changes where it is thought of giving
better performance or better portability. In addition, the code will be
gradually simplified and made more uniform and all architecture specific
-currently Intel- #ifdefs will be removed and abstracted away.
-------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : libhs5-vectorscan5
Version : 5.4.10.1-1.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 13.3 MiB
Installed : No
Status : not installed
Source package : vectorscan-5.4.10.1-1.2.src
Upstream URL : https://github.com/VectorCamp/vectorscan
Summary : Regular expression matching library
Description :
A fork of Intel's Hyperscan, modified to run on more platforms.
Vectorscan will follow Intel's API and internal algorithms where possible,
but will not hesitate to make code changes where it is thought of giving
better performance or better portability. In addition, the code will be
gradually simplified and made more uniform and all architecture specific
-currently Intel- #ifdefs will be removed and abstracted away.