[PATCH Libgpg-error] gpg-error.m4: support pkg-config

Werner Koch wk at gnupg.org
Tue Dec 4 08:27:37 CET 2018

On Mon,  3 Dec 2018 00:31, alon.barlev at gmail.com said:

> Please explain again why not give an option for downstream to build
> gnupg components using pkg-config, this does not take anything from
> whoever wishes to continue to use current mode.

Because supporting two build systems is a PITA and costs us too much.

The changes Gniibe did to support pgk-config for users of our libraries
were already expensive enough and it is not justified to burn more money
with that.  In particular because we and not you need to maintain such a
duplicated build systems.

After the next round of releases we can expect quite some extra work due
to these changes anyway.  We will take this trouble and thus pretty
please stop complaining about that not being sufficient.  There are much
more important things to do than to willy-nilly change an established
build system.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20181204/e60ff6ac/attachment.sig>

More information about the Gnupg-devel mailing list