Hi, Here is dependency analysis for wv:
The only package with "Depends: wv" is gwrite The only package with "Recommends: wv" is hyperestraier (I'm ignoring all the packages with "Suggests: wv") wv 1.2.4 and 1.2.9 are providing very same set of executables. Only two packages Depends on libwv-1.2-3: libabiword-2.9 python-abiword Only two source packages with libwv-dev in Build-Depends are: abiword pyabiword Here is the interesting part: pyabiword have libwv-dev in Build-Depends only as workaround against missing build-deps in libabiword-2.(8|9)-dev (which had empty Depends for years until it was reported by pyabiword maintainer Jonas Smedegaard and fixed by yours truly). Because python-abiword suffers from overlinking, it inherit dependency on libwv-1.2-3 from libabiword, but needlessly links against libwv. pyabiword builds perfectly with new libwv-1.2-4 (which is actually used only by libabiword). If pyabiword builded with --as-needed resulting binary package python-abiword do not depend on libwv at all. pyabiword maintainer is quite active, his latest pyabiword release dated January 17. Daniel, since I'm maintaining abiword which is the only known application using libwv (not to mention the same upstream) would you like me to become your co-maintainer for src:wv? (Sadly I can't promise to dedicate much attention to it, but anyway...) What do you think? Regards, Dmitry.
signature.asc
Description: This is a digitally signed message part.