From: Maxime Devos <maximedevos@telenet.be>
To: Efraim Flashner <efraim@flashner.co.il>, 55608@debbugs.gnu.org
Cc: Vagrant Cascadian <vagrant@debian.org>
Subject: [bug#55608] [PATCH] gnu: Add pbuilder.
Date: Tue, 24 May 2022 12:09:36 +0200 [thread overview]
Message-ID: <5f757b843a3ecc0c601adc87fcc5208ba3a415b5.camel@telenet.be> (raw)
In-Reply-To: <f5e751aede80501bb9bee5edf99e669c9b719d77.1653378760.git.efraim@flashner.co.il>
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
Efraim Flashner schreef op di 24-05-2022 om 10:59 [+0300]:
> + (add-after 'install-more 'wrap-programs
> + (lambda* (#:key native-inputs inputs outputs #:allow-other-keys)
> + (for-each
> + (lambda (file)
> + (wrap-script file
> + `("PATH" ":" prefix
> + (,(dirname (search-input-file (or native-inputs inputs) "/bin/cut"))
> + ,(dirname (search-input-file (or native-inputs inputs) "/bin/dpkg"))
> + ,(dirname (search-input-file (or native-inputs inputs) "/bin/grep"))
> + ,(dirname (search-input-file (or native-inputs inputs) "/bin/perl"))
> + ,(dirname (search-input-file (or native-inputs inputs) "/bin/sed"))
> + ,(dirname (search-input-file (or native-inputs inputs) "/bin/which"))
> + ,(dirname (search-input-file (or native-inputs inputs) "/sbin/debootstrap"))))))
Shouldn't these be inputs instead of native-inputs, because they will
end up being run when pbuilder is run? Likewise for'patch-source'.
Also, can be simplified to
[...] "PATH" ":" prefix ,(map (compose dirname (cut search-input-file inputs <>)) '("/bin/cut" "/bin/dpkg" ...)) [...]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-24 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 7:59 [bug#55608] [PATCH] gnu: Add pbuilder Efraim Flashner
2022-05-24 10:09 ` Maxime Devos [this message]
2022-05-25 8:41 ` [bug#55608] [PATCH v2] " Efraim Flashner
2022-05-29 13:03 ` bug#55608: " Efraim Flashner
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=5f757b843a3ecc0c601adc87fcc5208ba3a415b5.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55608@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=vagrant@debian.org \
/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).