[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[libmicrohttpd] Trying to understand libmicrohttpd versioning
From: |
Tomas Heran |
Subject: |
[libmicrohttpd] Trying to understand libmicrohttpd versioning |
Date: |
Mon, 13 Feb 2017 16:55:33 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 |
Hi,
I'm trying to understand versioning of the libmicrohttpd library, esp.
when it comes to LIB_VERSION_* variables in configure and the resulting
-version-info in libtool.
In our internal repository I'm upgrading from 0.9.37 to 0.9.52, i.e.:
(0.9.37) libmicrohttpd.so.10 -> libmicrohttpd.so.10.27.0
(0.9.52) libmicrohttpd.so.12 -> libmicrohttpd.so.12.40.0
I see that in public releases 0.9.45 and 0.9.46 the LIB_VERSION_AGE has
not been bumped (stayed the same at 34). That is puzzling as the libtool
versioning part of the documentation doesn't seem to be mentioning the
case when one would bump CURRENT, but leave AGE as is.
This effectively forces programs to be at least relinked (if not
rebuilt), because the libmicrohttpd.so.10 -> libmicrohttpd.so.10.27.0
no longer exists and is replaces by libmicrohttpd.so.12 ->
libmicrohttpd.so.12.40.0.
Now, I do see some "interfaces" removed, e.g. MHD_connection_close()
renamed to MHD_connection_close_(), but as far as I understand, that
function is not a public interface and so as far as the programs using
this library are concerned, the new version of the library should still
be backwards-compatible, i.e. programs linked with the older library
should still work fine without rebuilding and relinking.
What do I miss?
Thanks,
Tomas
--
Tomas Heran | +420220437150 | address@hidden
- [libmicrohttpd] Trying to understand libmicrohttpd versioning,
Tomas Heran <=