unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Guix-patches via <guix-patches@gnu.org>
To: 68043@debbugs.gnu.org
Cc: Josselin Poiret <dev@jpoiret.xyz>
Subject: [bug#68043] [core-updates PATCH] gnu: gpgme: Hardcode gpg binaries' location.
Date: Tue, 26 Dec 2023 17:47:50 +0100	[thread overview]
Message-ID: <9e065c4bc917a4e19a32c1ade0ebeab1fea8e9ff.1703609270.git.dev@jpoiret.xyz> (raw)

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





                 reply	other threads:[~2023-12-26 17:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9e065c4bc917a4e19a32c1ade0ebeab1fea8e9ff.1703609270.git.dev@jpoiret.xyz \
    --to=guix-patches@gnu.org \
    --cc=68043@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).