Package: d-shlibs
Version: 0.52
Severity: important
Bugs like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901771
indicate that d-devlibdeps is based on the assumption that the -dev
package for libfoo.so.2 will be libfoo2-dev. However, that naming
convention is discredited, and was specifically removed from Policy
4.0.0: see <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568374>
and <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493951>. The
recommendation is now to use libNAME[-]APIVERSION-dev if the upstream
developer plans to support multiple parallel-installable APIs (not
ABIs!), like GTK+ and libostree, or plain libNAME-dev if the upstream
developer only plans to support one API version at a time, like libfribidi
and libflatpak.
Since d-devlibdeps is based on an assumption that does not hold, it
will need to grow an increasingly long list of exceptions to the naming
convention that it assumes. I would recommend that packages should not
use d-devlibdeps, and d-shlibs should deprecate it.
smcv
