From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: 26608@debbugs.gnu.org
Subject: bug#26608: Provide --only-substitutes flag to "guix package --upgrade"
Date: Sun, 23 Apr 2017 01:03:52 +0200 [thread overview]
Message-ID: <87d1c4gi3r.fsf@gnu.org> (raw)
In-Reply-To: <874lxg77l4.fsf@dustycloud.org> (Christopher Allan Webber's message of "Sat, 22 Apr 2017 11:03:35 -0500")
Christopher Allan Webber <cwebber@dustycloud.org> skribis:
> Sometimes I do an upgrade and I want to get the latest security updates,
> but I also am not really available to burn through a lot of cpu time,
> (especially on my x200).
>
> I'd love it if thre were a flag so that I could specify "only bother to
> upgrade the packages where we only upgrade if a substitute is already
> available.
+1
> Note that I looked at the source to see if this would be an easy thing
> to add; I figured that this would be handled in roughly the same place
> as --keep-going or --fallback, but it looks to me like those are
> actually just passed over to the build daemon, so I'm not so sure how
> easy it would be to patch this in while we're still using Nix's C
> daemon? I'm not sure.
Clients could check, among the packages that are to be installed, which
ones are substitutable (with the ‘substitute-paths’ RPC or similar) and
filter out those that are not. No C++ involved.
Cheers,
Ludo’.
next prev parent reply other threads:[~2017-04-22 23:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 16:03 bug#26608: Provide --only-substitutes flag to "guix package --upgrade" Christopher Allan Webber
2017-04-22 23:03 ` Ludovic Courtès [this message]
2019-12-03 17:55 ` bug#26608: channels.scm supporting substitutes Nome Grey
2019-12-03 21:14 ` zimoun
2019-12-03 23:32 ` Nome Grey
2019-12-04 10:23 ` zimoun
2019-12-04 12:25 ` Nome Grey
2019-12-04 12:39 ` Nome Grey
2019-12-04 13:56 ` zimoun
2019-12-04 14:55 ` Nome Grey
2019-12-04 17:33 ` zimoun
2019-12-04 21:50 ` Nome Grey
2019-12-05 11:45 ` zimoun
2019-12-05 14:35 ` Nome Grey
2019-12-10 16:41 ` bug#32022: " 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=87d1c4gi3r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26608@debbugs.gnu.org \
--cc=cwebber@dustycloud.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.