Amos Jeffries <squ...@treenet.co.nz> writes: > I would have though this needs a soname bump. Otherwise software built > to use bcrypt might try to link to the old version with same soname.
My understanding is that one usually doesn't bump the soname when adding new functions. I was trying to look at how it has been done in gmp, but there it's all done via automake/libtool, which makes me slightly confused. But I think the current soname libgmp10.so dates from gmp-5.0.0 released 10 years ago, and there's been quite a few new public gmp functions added since then, e.g., the various mnp_sec_* functions used in Nettle. Then the soname only ensures that upgrading *the library* doesn't break installed and working applications. Upgrading an application (to a new version depending on new library functions) could break, and require library to be upgraded first. Preventing that kind of breakage has to be prevented by other means, e.g., dependencies in the packaging system. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
