Thanks for the quick turnaround. > Debian has identifier some potential problems, quoted from > <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788610#5>:
Ah, yes. The version script also sets a bunch of symbols to local scope. Good catch. Off the top of my head, the only sanity-check I can come up with is a brute force one: iterate through all referrers of ncurses, and check all their ELFs for missing symbols. > FWIW, there will only ever by one ‘version’ of a symbol, according to > upstream: > > <https://lists.nongnu.org/archive/html/bug-ncurses/2016-01/msg00018.html> > (also: <https://bugzilla.redhat.com/show_bug.cgi?id=1875587>) > > so I don't quite see the point. Agreed. I'm not sure it's worth the effort given the above. For in-tree packages, there is vanishing benefit, but my particular pain point was using a particular external pre-built .so. Oh well.
