wk at gnupg.org
Sun Sep 8 21:00:52 CEST 2013
On Sun, 8 Sep 2013 17:00, dkg at fifthhorseman.net said:
> is a compile-time check the right solution here? is this something we
> can detect at runtime instead?
I pondered with the runtiome check idea but compile time is fine because
1.6 is an ABI change.
> since libgcrypt 1.6 doesn't appear to have been released yet, i'm not
> sure if it will bump its SONAME from 11 (used by 1.5.3) to something
On GNU/Linux systems the SONAME will be 20. The git version already
uses that to avoid conflicts with the old ABI. Frankly, for most users
this ABI change will be invisible because only long deprecated or rarely
used functions are affected; technically it is one and thus the SONAME
needs to be changed.
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
More information about the Gnupg-devel