GPGME question: who uses /usr/include/{gpgmepp,qgpgme}_version.h ?

Daniel Kahn Gillmor dkg at
Mon Oct 31 20:01:21 CET 2016

Hi all--

i just realized that in addition to /usr/include/qgpgme/ and
/usr/include/gpgme++/, GPGME's development headers want to ship
/usr/include/qgpgme_version.h and /usr/include/libgpgmepp_version.h.

These files contain #define macros for the version information of the
library that's being built against.

What's the reason for having these two files at the same level
(/usr/include/) instead of shipping them inside the shipped directories?
For example, why not ship /usr/include/qgpgme/version.h instead?

On my own dev workstation, i see many more packages following the
foo/version.h approach:

    0 dkg at alice:~$ ls /usr/include/*/*version.h | wc -l
    0 dkg at alice:~$ ls /usr/include/*version.h | wc -l
    0 dkg at alice:~$ 

Is there a reason to use ${library}_version.h instead of putting the
file inside the shipped directory?  fwiw, if there's a concern about
backward compatibility, I've looked on and
i don't see anyone using these version.h files directly in debian at all
at the moment.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 930 bytes
Desc: not available
URL: </pipermail/attachments/20161031/34ede066/attachment.sig>

More information about the Gnupg-devel mailing list