From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: jgart <jgart@dismail.de>,
60868@debbugs.gnu.org, Lars-Dominik Braun <lars@6xq.net>
Subject: [bug#60868] [PATCH v2] build: pyproject-build-system: Use wrap-script instead of wrap-program.
Date: Tue, 24 Jan 2023 09:42:35 +0100 [thread overview]
Message-ID: <87y1pswcg4.fsf@gnu.org> (raw)
In-Reply-To: <20230123133354.1345-1-maxim.cournoyer@gmail.com> (Maxim Cournoyer's message of "Mon, 23 Jan 2023 08:33:54 -0500")
Hello!
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> * guix/build-system/pyproject.scm (default-guile): New procedure.
> (lower) Add guile to the host-inputs of the bag.
> * guix/build/pyproject-build-system.scm (wrap): Replace wrap-program with
> wrap-script. Rename bash-related nested variables/procedure with
> guile-related ones.
I had overlooked this patch before, sorry about that.
> + (host-inputs (modify-inputs inputs
> + (append (default-guile))))
Maybe add a comment stating it’s for ‘wrap-script’.
> + (define bindirs
> + (append-map (match-lambda
> + ((_ . dir)
> + (list (string-append dir "/bin")
> + (string-append dir "/sbin"))))
> + outputs))
Should it include “libexec”?
> + ;; Do not require "guile" to be present in the package inputs
> + ;; even when there is nothing to wrap.
> + ;; Also, calculate (guile) only once to prevent some I/O.
> + (define %guile (delay (search-input-file inputs "bin/guile")))
> + (define (guile) (force %guile))
Aaah, got it. :-)
LGTM, thanks!
Ludo’.
prev parent reply other threads:[~2023-01-24 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 20:37 [bug#60868] [PATCH] build: pyproject-build-system: Use wrap-script instead of wrap-program Maxim Cournoyer
2023-01-17 15:52 ` Maxim Cournoyer
2023-01-23 13:33 ` [bug#60868] [PATCH v2] " Maxim Cournoyer
2023-01-24 8:42 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1pswcg4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60868@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=maxim.cournoyer@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.