On 10.08.2012 16:47, Jakub Adam wrote: >> debian/patches/gammaray-probe-versioned-soname.patch: >> >> Why do you set a SONAME for gammaray_probe? >> When gammaray changes the ABI custom plugins will break anyway >> since you can't install different versions of gammaray. > > When SONAME is not set, lintian produces these warnings and error: > > W: gammaray: dev-pkg-without-shlib-symlink usr/lib/gammaray_probe.so > usr/lib/gammaray_probe.so > W: gammaray: shlib-without-versioned-soname usr/lib/gammaray_probe.so > gammaray_probe.so > E: gammaray: postinst-must-call-ldconfig usr/lib/gammaray_probe.so > > So the right solution is to override the warnings and add ldconfig call into > postinst script by hand?
Maybe a better solution would be to set the SONAME to the upstream version number. That way it's explicit that plugins need to be recompiled when the upstream version changes. >> debian/patches/harfbuzz-search-path.patch: >> >> What does this patch do? >> libqt4-private-dev doesn't contain the harfbuzz headers and that won't >> change at least until wheezy is released. > > I've already created a request for harfbuzz headers inclusion [1]. Right now, > that patch has no visible effect, but once the headers are available, it will > be enough to simply recompile gammaray to enable the additional features that > now can't be built. Ok. I'm a bit worried though that depending on more private Qt API will break GammaRay often. What do you think about joining the Debian Qt/KDE team and making the package team-maintained? Felix -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
