On 2021-09-26 12:16 +0200, Alec Leamas wrote: > > See https://wiki.debian.org/PkgKde/DhSymbolsFile > > After some tries in this area I have leaned to Russ Allberry's post > https://www.eyrie.org/~eagle/journal/2012-02/001.html. Is this outdated?
That KDE tool does help a lot but for large C++ packages symbols files are so large as to be of limited usefulness IMHO. If you are upstream too and actually know which symbols should be coming and going then they can have some utility as a check, but if you are just a packager struggling to keep up and all you ever do is generate a new one (as opposed to checking to see if the changes make sense) then I can't see the point. Having a much simpler shlibs file is more maintainable, and may be sufficient to track basic ABI/APi compatibility. > Is there a route where we keep things in experimental (bundled or not) and > let it stay there until wxWidgets 3.2 is out? Yes. This is what I'd do for the time being. That way you are not committed to this path where you might end up maintaining (or not maintaining, just hoping for the best on!) an unstable wxwidgets version for several years. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
signature.asc
Description: PGP signature
