unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 40612@debbugs.gnu.org
Subject: bug#40612: guix build system --dry-run is broken
Date: Sat, 18 Apr 2020 18:53:02 +0200	[thread overview]
Message-ID: <87y2qs68i9.fsf@gnu.org> (raw)
In-Reply-To: <87ftd1uc11.fsf@netris.org> (Mark H. Weaver's message of "Fri, 17 Apr 2020 15:50:23 -0400")

Hi Mark,

Mark H Weaver <mhw@netris.org> skribis:

> Yes, of course, I agree that it's not possible to present a build plan
> ahead of time when grafts are enabled.  That was the case before these
> changes, and it's the case today.
>
> The only part I don't understand is why you decided that "--dry-run"
> should no longer imply "--no-grafts".  Does it work better for other
> people?  For me, the "--dry-run" output has become utterly useless
> unless "--no-grafts" is included.

I explained the pros and cons of having ‘--dry-run’ no longer implying
‘--with-grafts’ here:

  https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00337.html

‘guix package --dry-run’ overall works well IME, except when a
dependency of a fixed-output derivation is missing, as explained above.

‘guix system’ doesn’t work so well as you note (though again, that
depends on what you’re building vs. what you have in store).

I think we must find the remaining places that lack “parallelism” and
address them, like I did for example in commit
2ad6eb0568ed69127aea987c009138e03b5b8954.  (It would help if that code
didn’t use the monadic interface this much because ‘lower-gexp’ already
does the right thing.)

> Anyway, it's not that important to me.  I can just fix it in my own
> private branch.  I filed this report because I thought it might benefit
> other users to have this fixed upstream.

It matters to every user so I think it’s worth fixing in our common code base.

Thanks,
Ludo’.

  reply	other threads:[~2020-04-18 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 21:31 bug#40612: guix build system --dry-run is broken Mark H Weaver
2020-04-14 15:16 ` Björn Höfling
2020-04-15 16:56   ` Ludovic Courtès
2020-04-17 19:50     ` Mark H Weaver
2020-04-18 16:53       ` Ludovic Courtès [this message]
2020-04-19 21:50         ` Mark H Weaver
2020-04-21 14:48           ` Ludovic Courtès

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=87y2qs68i9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=40612@debbugs.gnu.org \
    --cc=mhw@netris.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).