How to Install and Uninstall libhs5-vectorscan5 Package on openSUSE Leap
Last updated: November 07,2024
1. Install "libhs5-vectorscan5" package
This is a short guide on how to install libhs5-vectorscan5 on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
libhs5-vectorscan5
Copied
2. Uninstall "libhs5-vectorscan5" package
Here is a brief guide to show you how to uninstall libhs5-vectorscan5 on openSUSE Leap:
$
sudo zypper remove
libhs5-vectorscan5
Copied
3. Information about the libhs5-vectorscan5 package on openSUSE Leap
Information for package libhs5-vectorscan5:
-------------------------------------------
Repository : Update repository of openSUSE Backports
Name : libhs5-vectorscan5
Version : 5.4.9-bp155.4.3.8
Arch : x86_64
Vendor : openSUSE
Installed Size : 15.2 MiB
Installed : No
Status : not installed
Source package : vectorscan-5.4.9-bp155.4.3.8.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 : Update repository of openSUSE Backports
Name : libhs5-vectorscan5
Version : 5.4.9-bp155.4.3.8
Arch : x86_64
Vendor : openSUSE
Installed Size : 15.2 MiB
Installed : No
Status : not installed
Source package : vectorscan-5.4.9-bp155.4.3.8.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.