all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: Odd behavior with --dry-run and --upgrade
Date: Tue, 26 Jul 2016 00:14:47 +0200	[thread overview]
Message-ID: <8760rtbc14.fsf@gnu.org> (raw)
In-Reply-To: <87y44q8yta.fsf@gnu.org>


Ludovic Courtès writes:

> Hi!
>
> Alex Kost <alezost@gmail.com> skribis:
>
>> Roel Janssen (2016-07-23 18:11 +0300) wrote:
>>
>>> Dear Guix,
>>>
>>> For some time now, running `guix package --dry-run --upgrade' results in
>>> build actions involving grafting.  For a dry-run, I find that really
>>> odd.  I believe the correct behavior should be what can be achieved
>>> with: `guix package --dry-run --no-grafts --upgrade'.
>>
>> I'm totally agree with this; nowadays I always use --dry-run with
>> --no-grafts option.
>
> Same here…
>
>> As a user I expect that --dry-run means no building at all.
>>
>> BTW it's not just about ‘guix package --dry-run --upgrade’, it relates
>> to all commands, for example ‘guix build --dry-run foo’, etc.
>>
>> OTOH, if a future ‘--dry-run’ would mean what ‘--dry-run --no-grafts’
>> means now, than how to achieve what ‘--dry-run’ means now?  Or rather:
>> does anyone use just --dry-run (without --no-grafts)?  Is it really
>> useful?
>
> In theory it could be useful for ‘guix build’, since it’s a “low level”
> tool and people using it may want to be able to distinguish between
> grafted and non-grafted results.
>
> But honestly, I think changing ‘--dry-run’ to do ‘--dry-run --no-grafts’
> would be fine, and probably better than the current situation.

Could you provide some insight in where I should be looking to att the
check to 'graft?'?

Kind regards,
Roel Janssen

  parent reply	other threads:[~2016-07-25 22:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23 15:11 Odd behavior with --dry-run and --upgrade Roel Janssen
2016-07-23 18:23 ` Leo Famulari
2016-07-24  8:49 ` Alex Kost
2016-07-24 22:18   ` Ludovic Courtès
2016-07-25  7:46     ` Andreas Enge
2016-07-25 22:14     ` Roel Janssen [this message]
2016-07-26  9:50       ` Ludovic Courtès
2016-07-26 10:20         ` Roel Janssen
2016-07-26 12:41           ` Ludovic Courtès
2016-07-27 12:09             ` Alex Kost
2016-07-27 22:19               ` Ludovic Courtès
2016-07-28  7:58                 ` Alex Kost
2016-07-28 13:01                   ` Ludovic Courtès
2016-07-30 15:25                     ` Alex Kost
2016-07-30 22:51                       ` Ludovic Courtès
2016-07-26 13:41         ` Alex Kost
2016-07-26 14:37           ` Ludovic Courtès
2016-08-21  4:54         ` Roel Janssen
2016-08-27 23:23           ` Roel Janssen
2016-08-28 14:08           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8760rtbc14.fsf@gnu.org \
    --to=roel@gnu.org \
    --cc=alezost@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.