From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 04/05: gnu: autoconf: Support cross-build.
Date: Thu, 23 Apr 2020 07:45:12 +0200 [thread overview]
Message-ID: <874ktaoivr.fsf@gnu.org> (raw)
In-Reply-To: <87lfmnqlrc.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 22 Apr 2020 23:00:07 +0200")
Ludovic Courtès writes:
Hi!
>> Tests are disabled currently (even on master!), so I guess that
>> inserting this line break is fine :-)
>
> Damn it, this is terrible! But not your fault, for sure. :-)
Yes, it would be good to re-enable them during the next cycle.
>> - (arguments `(#:tests? #f))
>> + (arguments
>> + `(#:tests? #f
>
> I’m really nitpicking, but could you move the XXX comment right after
> #:tests? #f?
As checkn on IRC: yes, right after "(arguments `(" right before #:tests
>> + (out (assoc-ref outputs "out"))
>> + (store-directory (%store-directory)))
>> + (substitute* (find-files (string-append out "/bin"))
>> + (((string-append store-directory "/[^/]*-m4-[^/]*")) m4)
>> + (((string-append store-directory "/[^/]*-perl-[^/]*"))
>> + perl))
>
> I’m very much in favor of keeping regexps literal. What about writing
> them as:
>
> (substitute* …
> (("/[[:graph:]]/bin/m4")
> (string-append m4 "/bin/m4"))
> …)
After discussing various options on IRC: keeping the parenthetical
(((string-append stor-directory...; we are using than for git and
perl, see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40698#16
> Also please move the comment right below ‘lambda*’. :-)
Done!
> And then I think you can push it to ‘core-updates’.
Pushed to core-updates, together with a simalar patch for automake,
and a trivial one for texinfo.
Thanks!
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2020-04-23 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200419090521.13083.63849@vcs0.savannah.gnu.org>
[not found] ` <20200419090523.C255A2049B@vcs0.savannah.gnu.org>
2020-04-21 16:01 ` 04/05: gnu: autoconf: Support cross-build Ludovic Courtès
2020-04-21 18:12 ` Jan Nieuwenhuizen
2020-04-21 18:23 ` Jan Nieuwenhuizen
2020-04-22 21:00 ` Ludovic Courtès
2020-04-23 5:45 ` Jan Nieuwenhuizen [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
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=874ktaoivr.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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).