On Fri, 2018-03-30 at 09:29 +0200, Niels Möller wrote:
Daniel P. Berrangé berrange@redhat.com writes:
The traditional way is for developers to update the dependancies to have an explicit version against the library they require. eg if libvirt requires some symbol introduced in nettle x.y, the maintainer would add
Requires: nettle >= x.y
the problem is that humans are fallible and so these versioned dependancies frequently get missed, because package maintainers don't often have accurate info on which min version is needed by a build.
I agree it's going to be a bit brittle to do that manually. E.g., in the example at hand, the package source code only used the old nettle_hashes symbol, but the new version of nettle headers turned that into a macro calling a new function.
A colleague is working on a script to automate that version script creation. That tool is on its infancy, but if you find it useful please send feedback at: https://github.com/ansasaki/symbol_version
The idea is that if the exported symbols per release can be provided to the script, it will create the right symbol map file.
regards, Nikos