Dear Richard, On Wed, Apr 02, 2008 at 11:27:59PM +0200, Richard B. Kreckel wrote:
Anyway, I have two options now:
a) Release CLN-1.2.2 with changed soname, although the ABI did not change wrt. CLN-1.2.1.
I think this is the only sane thing to do.
b) Just ignore it and release CLN-1.2.2 as libcln.so.5. Seriously.
This breaks every program/library linked with CLN-1.2.0 upon the upgrade (even if the library in question uses CLN only internally). Such breakage is not really wellcome.
I am under the impression that the amount of trouble incurred by just re-building GiNaC for all distros is dwarfed by the trouble induced by a soname bump.
This breaks every user-compiled library/program when libcln5 package is upgraded (from version 1.2.0-* to 1.2.2-*). It's not really wellcome. Best regards, Alexei -- All science is either physics or stamp collecting.