On Fri, 13 Feb 2015 22:13:21 +0100 Hilko Bengen <ben...@debian.org> wrote: > 1. Override upstream's decision to change the SONAME with every release. > I am not entirelysure how stable libhtp's API/ABI should be > considered -- looking at changes and deciding on compatibility issues > making those decisions would certainly put a burden on the maintainer > in the future (although the .symbols mechanism helps for obvious > cases such as removed APIs.) > > I am attaching a patch to drop the -release parameter from the > libtool call, libhtp.so.1.0.0 (instead of libhtp-0.5.15.so.1.0.0) is > generated. The .symbols file would need to be updated to reflect that > change, too, of course.
1bis/ If you don't override the SONAME, then you should make sure to generate strong dependencies like "libhtp1 (>= 0.5.15~), libhtp1 (<< 0.5.16)" But you should not allow packages to get built with a lax dependency... Note that updating libhtp to 0.5.17 will currently generate a file conflict with suricata (see #783005). Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
