From: Maxime Devos <maximedevos@telenet.be>
To: 57659@debbugs.gnu.org, mail@cbaines.net, kiasoc5@disroot.org
Subject: [bug#57659] [PATCH v3] gnu: Add blesh.
Date: Thu, 15 Sep 2022 17:26:30 +0200 [thread overview]
Message-ID: <4aa38651-563e-000f-3bb0-7a36f01bad6f@telenet.be> (raw)
In-Reply-To: <87edwe8hyn.fsf@cbaines.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 1509 bytes --]
On 14-09-2022 10:40, Christopher Baines wrote:
>
> kiasoc5 <kiasoc5@disroot.org> writes:
>
>> Tests pass now.
>>
>> * gnu/packages/bash.scm (blesh): New variable.
>> ---
>> gnu/packages/bash.scm | 45 +++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 45 insertions(+)
>
> Thanks. I've tweaked the name of one of the phaess (use-LANG-for-tests
> rather than use-LC_ALL-for-tests) as that seemed more correct. I also
> removed some inputs that were redundant (coreutils is provided by the
> gnu-build-system, so is an implicit input), and git-minimal didn't seem
> to be required.
gnu-build-system only provides a _natively compiled_ coreutils (for
--system), not a cross-compiled coreutils (for --target). As such, it
is not redundant (unless it compile-time only (*), the build system
isn't clear to me).
>+ (add-after 'unpack 'make-readlink-work
>+ (lambda _
>+ (substitute* "ble.pp"
>+ (("PATH=/bin:/usr/bin readlink")
>+ (search-input-file %build-inputs
>+ "/bin/readlink")))))
You're mixing G-exp (new) and %build-inputs (old). How about
(search-input-file inputs "bin/readlink") or (which "readlink")
(depending on whether inputs or native-inputs is appropriate) instead?
Greetings,
Maxime.
(*) can be verified by using "guix gc --references".
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-09-15 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 2:11 [bug#57659] [PATCH] gnu: Add blesh kiasoc5 via Guix-patches via
2022-09-11 19:59 ` Christopher Baines
2022-09-13 2:32 ` [bug#57659] [PATCH v2] " kiasoc5 via Guix-patches via
2022-09-13 12:02 ` Maxime Devos
2022-09-14 3:07 ` [bug#57659] [PATCH v3] " kiasoc5 via Guix-patches via
2022-09-14 8:40 ` bug#57659: " Christopher Baines
2022-09-15 15:26 ` Maxime Devos [this message]
2022-09-16 0:05 ` [bug#57659] " kiasoc5 via Guix-patches via
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=4aa38651-563e-000f-3bb0-7a36f01bad6f@telenet.be \
--to=maximedevos@telenet.be \
--cc=57659@debbugs.gnu.org \
--cc=kiasoc5@disroot.org \
--cc=mail@cbaines.net \
/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).