> If some changes were done to fix the compilation, it means that some people still use a libgcrypt version older than 1.6.0.
> And as seen in our CMakeLists.txt file, the minimum version required for now is 1.5.0.
I understand your reluctancy to upgrade the requirements, but don’t you think that ten years is a *very long* time to support
an old cryptographic library (libgcrypt 1.5.0 was released in 2011-06-29), just because somebody out there might still be using it?
Matthias
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
