On Wed, Aug 05, 2015 at 08:40:34AM +0100, Simon McVittie wrote: > Longer-term, I think this is a symptom of not generating correct library > dependencies in xapian-core, which could affect any consumer of its API, > not just xapian-omega
It's actually exactly the source level dependency that this is aiming to ensure - because they share an upstream and are released together, xapian-omega has a tendency to make use of any API additions in the latest xapian-core. It's tedious to have to remember to check if this is the case for each new release packaged, and I upload new upstream versions together anyway, so I just automated the assumption. Most packages using the Xapian API tend to be conservative about hard requiring new versions of xapian-core, so this just isn't an issue for most packages. > it should ideally have a .symbols file > <https://wiki.debian.org/UsingSymbolsFiles> but failing that, My understanding was that symbol files for C++ libraries was still not a clear win - is rra's summary here now out of date? https://lists.debian.org/debian-devel/2012/01/msg00727.html > using dh_makeshlibs -V would be the next best thing. That doesn't seem to do what I want at all. Cheers, Olly
