Should I bump cryptopp soname?

[nucleo]

No need to bump soname now.
Problem fixed by patching config.h both for i686 and x86_64.
Thanks Kevin Kofler for patch.

Alexey Kurov <nucleo at fedoraproject.org>

> Hi,
> 
> Need help with soname for new libcryptopp build.
> 
> One of previous cryptopp versions built with
> disabled SSE2 for x86 because it doesn't built with SSE2.
> See http://groups.google.com/group/cryptopp-users/browse_thread/thread/d639907b0b1816b9
> 
> This was done by adding in config.h line (only for x86)
> #define CRYPTOPP_DISABLE_SSE2
> 
> But negative side of this was conflict when installing
> both cryptopp-devel i686 x86_64 packages.
> See bug https://bugzilla.redhat.com/show_bug.cgi?id=645169
> 
> config.h is in cryptopp-devel and was used for building other apps (amule and other).
> 
> Last cryptopp 5.6.1 not needs disabling SSE2 for building on x86
> but I can't just build it without patched config.h because
> amule will crash when using this cryptopp build.
> 
> If I rebuild amule against new cryptopp build it will not crash.
> 
> So should I bump libcryptopp soname to .so.7 when building it
> with enabled SSE2 because of binary incompatibility with .so.6?
> 
> Soname not set by Crypto++ upstream and was
> manually added with autotools patch
> 
> Alexey Kurov <nucleo at fedoraproject.org>