[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#68043] [core-updates PATCH] gnu: gpgme: Hardcode gpg binaries' loca
From: |
Josselin Poiret |
Subject: |
[bug#68043] [core-updates PATCH] gnu: gpgme: Hardcode gpg binaries' location. |
Date: |
Tue, 26 Dec 2023 17:47:50 +0100 |
From: Josselin Poiret <dev@jpoiret.xyz>
* gnu/packages/gnupg.scm (gpgme): Pass the gpg binaries' location to configure.
Change-Id: I13d8e4d97cd93fffa6e3d1a6e39972e08ed69376
---
Hi everyone,
I just realized that our gpgme relies on having gpg and friends in its PATH,
which leads to troublesome errors for shepherd daemons using it (e.g. fwupd).
Here is a simple patch that fixes it, but it causes 3k+ rebuildss. I've tagged
it core-updates, but it's probably not going to go there. WDYT?
gnu/packages/gnupg.scm | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
index 2b6a5ec796..1ae0e78f50 100644
--- a/gnu/packages/gnupg.scm
+++ b/gnu/packages/gnupg.scm
@@ -416,7 +416,12 @@ (define-public gpgme
(sha256
(base32 "17hfigfnq6xz45b5xrp299f68b5mwx0aysd51sx5v4nf8yp4w79n"))))
(build-system gnu-build-system)
- (native-inputs
+ (arguments
+ (list
+ #:configure-flags
+ #~(let ((gpg-bins (dirname (search-input-file %build-inputs
"/bin/gpg"))))
+ (list (string-append "--enable-fixed-path=" gpg-bins)))))
+ (inputs
(list gnupg))
(propagated-inputs
;; As required by the pkg-config's Requires.private.
base-commit: 5bd80ccd69047b1777749e24d4adf2c951b5d14b
--
2.41.0
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug#68043] [core-updates PATCH] gnu: gpgme: Hardcode gpg binaries' location.,
Josselin Poiret <=