Closed issue by Chocimier on void-packages repository

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

Description:
Something is wrong with shlibs checking on #14511, but i am not exactly sure what.

Story:

libvterm-0.0.20151229 provides libvterm.so.0, a symlink to libvterm.so.0.0.0
libvterm-0.1.1 provides libvterm.so.0, a symlink to libvterm.so.0.1.1
both provide libvterm.so, a symlink to real libvterm.so.0.?.?
libvterm.so.0.1.1 provides symbols not provided by libvterm.so.0.0.0

neovim-0.4.2 is linked against libvterm.so.0 provided by newer libvterm

xbps-src reads from shlibs that libvterm.so.0 is provided by libvterm>=0.0.20151229
xbps-src generates neovim package with run dep libvterm>=0.0.20151229

xbps don't update libvterm on update of neovim

neovim fails to start because of missing symbols in libvterm.so.0

Question: what is wrong:
- libvterm providing incompatible versions of libvterm.so.0, even if not telling to use them?
- toolchain linking against libvterm.so.0 symlink, not explicitly instructed to do so?
- xbps-src specifying symlink in shlibs?