why should i rebuild my app when a new version of jsoncpp rpm package is released

[sepavel]

Hello,

Now, if I dynamically link the jsoncpp library, it is linked with a version specified by SOVER and when the library is updated (as RPM package), the application needs to be rebuilt

Are there any approaches to avoid this other than static linking?

Regards,
Pavel

[baylesj]

I think JsonCpp has been a little aggressive about SOVERSION incrementation, and that's mostly my responsbility. I think in the future us being more cautious of SOVERSION bumps and not doing it unless absolutely necessary should help this some.

An SOVERSION bump should indicate that you need to rebuild because an API has changed. I think with our last few bugfix releases, I was overly cautious and bumped the version even though it wasn't necessary (I think rebuilding is better than a difficult to resolve library crash because the API boundary broke but the so version is the sam).

I'll try to be more careful with SOVERSION bumps in the future, hopefully that helps.