From: Efraim Flashner <efraim@flashner.co.il>
To: Remco van 't Veer <remco@remworks.net>
Cc: help-guix@gnu.org
Subject: Re: guix package -u . --dry-run equivalent for guix home
Date: Thu, 7 Dec 2023 12:05:11 +0200 [thread overview]
Message-ID: <ZXGY10yaMSgnqZUP@3900XT> (raw)
In-Reply-To: <874jguwghk.fsf@remworks.net>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On Thu, Dec 07, 2023 at 09:42:47AM +0100, Remco van 't Veer wrote:
> 2023/12/06, Efraim Flashner:
>
> >> Is it possible to get an package update dry-run like output for guix
> >> home?
> >
> > I'll run 'guix home build <path-to-file> -n' to see what's going to be
> > built.
>
> That's a bit more informative but currently it only tells me it's going
> to download some new version of guix. Running build without -n reveals
> it will download and install a lot more..
>
> How are people (with update junky tendencies like me) using guix-home?
> Run guix-home-reconfigure after every guix-pull?
Ok, I admit that isn't the full command.
guix home build <path-to-file> --no-grafts -n'
The '--no-grafts' means it'll give an accurate response of what will be
built/downloaded without taking into account any new grafts.
I also normally add '--fallback' with 'guix home build' to try again if
a download fails.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-07 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 8:58 guix package -u . --dry-run equivalent for guix home Remco van 't Veer
2023-12-06 20:36 ` Efraim Flashner
2023-12-07 8:42 ` Remco van 't Veer
2023-12-07 10:05 ` Efraim Flashner [this message]
2023-12-09 17:48 ` Remco van 't Veer
2023-12-07 13:24 ` Tomas Volf
2023-12-09 17:55 ` Remco van 't Veer
2023-12-10 0:20 ` Tomas Volf
2023-12-10 8:13 ` Remco van 't Veer
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=ZXGY10yaMSgnqZUP@3900XT \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=remco@remworks.net \
/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).