How to Install and Uninstall libsearpc1 Package on openSUSE Leap
Last updated: February 24,2025
1. Install "libsearpc1" package
This tutorial shows how to install libsearpc1 on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
libsearpc1
Copied
2. Uninstall "libsearpc1" package
This guide let you learn how to uninstall libsearpc1 on openSUSE Leap:
$
sudo zypper remove
libsearpc1
Copied
3. Information about the libsearpc1 package on openSUSE Leap
Information for package libsearpc1:
-----------------------------------
Repository : Main Repository
Name : libsearpc1
Version : 3.3.0.20220902-bp155.1.7
Arch : x86_64
Vendor : openSUSE
Installed Size : 56.2 KiB
Installed : No
Status : not installed
Source package : libsearpc-3.3.0.20220902-bp155.1.7.src
Upstream URL : https://github.com/haiwen/libsearpc/
Summary : Library to handle the serialization/deserialization part of RPC
Description :
Searpc is a simple C language RPC framework based on GObject system. Searpc handles the serialization/deserialization part of RPC, the transport part is left to users.
The serialization/deserialization uses JSON format via json-glib library. A serialized json object is returned from server to client after executing the RPC function. Each RPC function defined in the server side should take an extra GError argument to report error.
-----------------------------------
Repository : Main Repository
Name : libsearpc1
Version : 3.3.0.20220902-bp155.1.7
Arch : x86_64
Vendor : openSUSE
Installed Size : 56.2 KiB
Installed : No
Status : not installed
Source package : libsearpc-3.3.0.20220902-bp155.1.7.src
Upstream URL : https://github.com/haiwen/libsearpc/
Summary : Library to handle the serialization/deserialization part of RPC
Description :
Searpc is a simple C language RPC framework based on GObject system. Searpc handles the serialization/deserialization part of RPC, the transport part is left to users.
The serialization/deserialization uses JSON format via json-glib library. A serialized json object is returned from server to client after executing the RPC function. Each RPC function defined in the server side should take an extra GError argument to report error.