From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#26608: Provide --only-substitutes flag to "guix package --upgrade" Date: Sun, 23 Apr 2017 01:03:52 +0200 Message-ID: <87d1c4gi3r.fsf@gnu.org> References: <874lxg77l4.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58190) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d245R-00061y-St for bug-guix@gnu.org; Sat, 22 Apr 2017 19:05:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d245O-0008MW-Oq for bug-guix@gnu.org; Sat, 22 Apr 2017 19:05:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:36664) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d245O-0008MR-LH for bug-guix@gnu.org; Sat, 22 Apr 2017 19:05:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d245O-0007R0-AZ for bug-guix@gnu.org; Sat, 22 Apr 2017 19:05:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <874lxg77l4.fsf@dustycloud.org> (Christopher Allan Webber's message of "Sat, 22 Apr 2017 11:03:35 -0500") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Christopher Allan Webber Cc: 26608@debbugs.gnu.org Christopher Allan Webber 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 =E2=80=98substitute-paths=E2=80=99 RPC or = similar) and filter out those that are not. No C++ involved. Cheers, Ludo=E2=80=99.