About the manual (gcrypt.texi)
peter at lekensteyn.nl
Wed Feb 8 14:55:42 CET 2017
While reading the manual I noticed this text:
> Libgcrypt is developed using a Subversion3 repository.
This should probably be changed to Git.
> Although all released versions are tagged in this repository, they
> should not be used to build production versions of Libgcrypt. Instead
> released tarballs should be used.
This part I do not really understand, why would a git tag where you
manually run autogen.sh be different? Have there been issues in the
More information about the Gcrypt-devel