There was discussion of installing the gnupg-2.1 binaries 'gpg2' and
'gpgv2' as 'gpg' and 'gpgv' on the 'Trustable guix pull' thread [0].
If we do this, it will become impossible to install gnupg-1 and
gnupg-2.1 in the same profile, due to collisions of 'gpg' and 'gpgv' and
their man pages. There are no collisions without this change.
It might also require users to update their scripts.
On the other hand, Werner recommends the change.
The configuration option does not exist for gnupg-2.0.
Discussion welcome!
[0]
http://lists.gnu.org/archive/html/bug-guix/2016-06/msg00035.html
>From d9da5767601a8a10ade206ff186332ed0b1a2645 Mon Sep 17 00:00:00 2001
From: Leo Famulari <l...@famulari.name>
Date: Mon, 13 Jun 2016 15:39:15 -0400
Subject: [PATCH] gnu: gnupg-2.1: Install executable as 'gpg'.
* gnu/packages/gnupg.scm (gnupg-2.1)[arguments]: Add '--enable-gpg2-is-gpg'
to #:configure-flags.
---
gnu/packages/gnupg.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
index e6583e5..849a0b6 100644
--- a/gnu/packages/gnupg.scm
+++ b/gnu/packages/gnupg.scm
@@ -234,7 +234,8 @@ compatible to GNU Pth.")
("sqlite" ,sqlite)
("zlib" ,zlib)))
(arguments
- `(#:phases
+ `(#:configure-flags '("--enable-gpg2-is-gpg")
+ #:phases
(alist-cons-before
'configure 'patch-config-files
(lambda _
--
2.8.4
