unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: jgart <jgart@dismail.de>, Guix Help <help-guix@gnu.org>
Subject: Re: which package gets built first?
Date: Fri, 04 Nov 2022 10:49:21 +0100	[thread overview]
Message-ID: <86wn8b3v8e.fsf@gmail.com> (raw)
In-Reply-To: <20221104003432.GB9043@dismail.de>

Hi,

On Fri, 04 Nov 2022 at 00:34, jgart <jgart@dismail.de> wrote:
> What determines which package gets built first in the following invocation?
>
> `guix build emacs-zig-mode zig`

It depends. :-)  Usually, something like

  guix thing stuff1 stuff2

is processed in that order: stuff2 then stuff1.  Other said, the CLI is
somehow parsed from right to left.  For instance, see bug#43585 [1] or
bug#50473.  Well, compare:

--8<---------------cut here---------------start------------->8---
$ guix package --show=emacs --show=zig | recsel -Cp name
name: zig
name: emacs

$ guix package --show=zig --show=emacs  | recsel -Cp name
name: emacs
name: zig
--8<---------------cut here---------------end--------------->8---

(Note that “guix show” process from left to right since it is how most
of us type and read.)


That’s said, “guix build” is special.  Because it somehow processes the
topological order between stuff1 and stuff2.  Other said, if stuff2
depends on stuff1, then it first builds stuff1 then second stuff2.


1: <http://issues.guix.gnu.org/issue/43585>
2: <http://issues.guix.gnu.org/issue/50473>


Cheers,
simon


  parent reply	other threads:[~2022-11-04 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  5:34 which package gets built first? jgart
2022-11-04  5:35 ` jgart
2022-11-04  9:49 ` zimoun [this message]
2022-11-04 16:39   ` (
2022-11-04 19:40     ` zimoun

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=86wn8b3v8e.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.de \
    /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.
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).