Dynamically linked libssl messes portability of v0.1.0 #19
Description
Description:
The first release of patch-hub, version 0.1.0, includes a binary of patch-hub for the target x86_64-unknown-linux-gnu. As mentioned in #18, this target dynamically links objects but should work seamlessly despite it.
While testing the installation of this pre-compiled version of patch-hub in containers for Debian, Archlinux, and Fedora, I noticed that it tries to link to a specific implementation of libssl, namely libssl.1.1, which (for the images used) makes the app fail to launch. I fear this behavior may happen in other contexts besides containers...
How to reproduce:
Install version 0.1.0 by downloading the compressed release, decompressing it, and launching the patch-hub executable. You probably will encounter an error such as
patch-hub: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
Expected behavior:
This behavior kills the application...
Screenshots
Setup:
Screenshot setup: Docker-Hub archlinux:latest image - digest 0db05c077b83
Release version: version 0.1.0