New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/36619#issuecomment-1186593922

Comment:
> You can't just create a soname to a incompatible library version and even worse, make the build system using it (setting bogus shlib_provides). this is not improving Void in any form, just making it broken (therefore used "bogus" to describe that)

It's not incompatible. The issue is Debian doing Debian things and naming their libcurl after the TLS library used to build it, for whatever license compatibility reason. The libcurl API/ABI is the same across the library versions.

We removed the workaround from the curl package because that felt like the wrong place for it; it's not really our place to provide this fix.

> I was thinking about asking the support to create a "static" version of their plugins, this should be sufficient to run it everywhere, even on Void.

How would that work? If plugins are dlopened, linking them as statically as possible can be complicated business.