unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 39945-done@debbugs.gnu.org
Subject: bug#39945: [PATCH 0/1] Introducing 'with-parameters' for gexp dynamic binding
Date: Thu, 12 Mar 2020 18:34:03 +0100	[thread overview]
Message-ID: <87eetxqxys.fsf@gnu.org> (raw)
In-Reply-To: <87pndpeo8d.fsf@gmail.com> (Mathieu Othacehe's message of "Fri, 06 Mar 2020 12:06:58 +0100")

Hi Mathieu,

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

>> Thoughts?
>>
>> Besides, ‘with-parameters’ is the dual of what was discussed at
>> <https://issues.guix.gnu.org/issue/29296>.
>
> Super nice! Maybe you could add a test-case involving
> %current-target-system but otherwise this LGTM.

Done and pushed as cf2ac04f13d9266c7c8a2ebd2e85ef593231ac9d.

> Do you think we could use this to get around this issue we discussed
> there:
> https://lists.gnu.org/archive/html/guix-devel/2019-12/msg00099.html.

It could be use to achieve the same result as the <native-qemu> package
you proposed:

  #~(… #+(with-parameters ((%current-system %system)) qemu) …)

However, the issue I mentioned before with this approach remain:

  […] now the result of:

    guix system build -s armhf-linux -d …

  would be dependent on the actual system type.  In other words, the
  result would be different if you run it on armhf-linux, if you run it on
  x86_64-linux, or if you run it on i686-linux.  Not great.

Thanks for your feedback!

Ludo’.

      reply	other threads:[~2020-03-12 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06 10:41 [bug#39945] [PATCH 0/1] Introducing 'with-parameters' for gexp dynamic binding Ludovic Courtès
2020-03-06 10:53 ` [bug#39945] [PATCH 1/1] gexp: Add 'with-parameters' Ludovic Courtès
2020-03-06 11:06 ` [bug#39945] [PATCH 0/1] Introducing 'with-parameters' for gexp dynamic binding Mathieu Othacehe
2020-03-12 17:34   ` 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

  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=87eetxqxys.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39945-done@debbugs.gnu.org \
    --cc=m.othacehe@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 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).