[Tomi Ollila] Re: [PATCH 2/2] test: use gpgconf --create-socketdir if available

I'm pretty sure Tomi meant to complain publicly ;). --- Begin Message --- On Tue, Feb 14 2017, David Bremner wrote: > This enables the shortened socket pathes in /run or equivalent. The > explicit call to gpgconf is needed for nonstandard GNUPGHOME settings. 2½ comments

Re: [PATCH 2/2] test: use gpgconf --create-socketdir if available

On Tue, Feb 14 2017, David Bremner wrote: > This enables the shortened socket pathes in /run or equivalent. The > explicit call to gpgconf is needed for nonstandard GNUPGHOME settings. 2½ comments inline: __> --- > test/test-lib.sh | 14 ++ > 1 file changed, 14

Re: [PATCH 2/2] test: use gpgconf --create-socketdir if available

Daniel Kahn Gillmor writes: > 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? Maybe once a gnupg bug

Re: [PATCH 2/2] test: use gpgconf --create-socketdir if available

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

[PATCH 2/2] test: use gpgconf --create-socketdir if available

This enables the shortened socket pathes in /run or equivalent. The explicit call to gpgconf is needed for nonstandard GNUPGHOME settings. --- test/test-lib.sh | 14 ++ 1 file changed, 14 insertions(+) diff --git a/test/test-lib.sh b/test/test-lib.sh index 86e792a8..9aa6163b 100644