On Tue 2017-02-14 16:42:39 -0500, David Bremner wrote: > This enables the shortened socket pathes in /run or equivalent. The > explicit call to gpgconf is needed for nonstandard GNUPGHOME settings.
For the current GnuPG 2.1.18, this pair of patches looks reasonable to me, and it should indeed solve builds in deeply-nested paths. That said, i currently consider this a workaround to a bug that should really be fixed in GnuPG itself, as i noted on gnupg-users: https://lists.gnupg.org/pipermail/gnupg-users/2017-February/057692.html id:87k28rl6o8....@alice.fifthhorseman.net I'd love to not see this kind of workaround cruft pile up, because it tends to cause problems in the future. is there a way that we can mark this sort of thing for fairly prompt removal once it's fixed upstream? --dkg
signature.asc
Description: PGP signature
_______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
