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.
2. Since suricata is the only reverse dependency of libhtp and
contains
a copy of libhtp within its source tarball, so we could drop the
libhtp package altogether and use that embedded copy instead, at
least for the jessie release.
3. Change the binary package name to reflect the SONAME -- for
instance
libhtp-0.5.15. I believe that we are too late in the freeze to be
adding new binary package names.