On 12/8/20 9:57 PM, José Luis Blanco-Claraco wrote: > Hi Matthias: > > I'm curious about the rationale of not using libbinutils as shared > libraries... sorry if this seems a stupid question! > > The dependency was added in this last version to enable using BFD to > find debug info in binaries and expose that in the upstream library > functionality.
There is no public API for libopcodes and libbfd. Even the ABI may change with any update on a release branch or on trunk. The best thing is to avoid such dependencies, second best option is to not rely on the shared library, and only linking with the static libaries (and in this case documenting that with the Built-Using: attribute). Matthias > Cheers, > JL > > On Tue, Dec 8, 2020 at 7:51 AM Matthias Klose <d...@debian.org> wrote: >> >> Package: src:mrpt >> Version: 1:2.1.5-1 >> Severity: serious >> Tags: sid bullseye >> >> mrpt uses private binutils shared libraries: >> >> Package: libmrpt-core2.1 >> Depends: libbinutils (>= 2.35.1), libbinutils (<< 2.35.2), [...] >> >> Please don't do this. Either disable the use of these libraries, or >> link these statically and add a Built-Using attribute to the binary package. > > >
