Re: shlibs checking fail on neovim update

[voidlinux-github@inbox.vuxu.org]

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/14856#issuecomment-569419722

Comment:
This is a more general issue, adding new symbols doesn't break the ABI so they don't really have to bump the version.
The same happens with glibc and libressl, where we just bump the the minimum version in `common/shlibs` so packages build against a new `glibc` or `libressl` version that might use a new or in glibcs case a new versioned symbol will not break and depend on the new version.

Not sure what we can do about it, we could just depend on `>=` of the exact package version we linked against instead of `common/shlibs` but then selective/partial updates and installs become a lot less doable.

Edit:
The best solution would be a way to not just record SONAMEs but also record earch symbol and then check the compiled binaries needed symbols against the record and then take the highest version of the required symbols as minimum version instead of `common/shlibs` version.