From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Upgrading packages with substitutes only (bug #26608)
Date: Mon, 19 Jun 2017 10:23:52 +1000 [thread overview]
Message-ID: <87vansrfjb.fsf@zancanaro.id.au> (raw)
In-Reply-To: <1497807874.3904845.1013277520.762D17E8@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On Sun, Jun 18 2017, Timothy Sample wrote:
> While the user experience would suffer a bit, it’s no real hardship to
> type
>
> $ guix package \
> --do-not-upgrade $(guix package --only-substitutes -u) \
> -u
>
> This is definitely possible.
Just checking: is the proposal that --only-substitutes /always/ prints a
list of packages without substitutes? My understanding was that it would
only print the list if there were packages without substitutes (thus
making the above potentially incorrect/wasteful if everything has a
substitute, because you shouldn't unconditionally re-run `guix
package`). I don't know if we should conflate "upgrade my profile" with
"print a list of packages without substitutes". Those aren't the same
requests.
I'm more in favour of it continuing and building the new profile, but
printing a list of packages which didn't have substitutes. If the user
wants to roll-back the upgrade then they can easily do so, but they
asked for it to be upgraded and we can still do that.
Carlo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-06-19 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 19:28 Upgrading packages with substitutes only (bug #26608) Timothy Sample
2017-06-17 22:34 ` Ludovic Courtès
2017-06-18 9:38 ` Ricardo Wurmus
2017-06-18 16:11 ` Leo Famulari
2017-06-18 17:44 ` Timothy Sample
2017-06-18 21:44 ` Ricardo Wurmus
2017-06-19 0:23 ` Carlo Zancanaro [this message]
2017-06-19 17:33 ` Leo Famulari
2017-06-19 12:02 ` Ludovic Courtès
2017-06-19 17:25 ` Timothy Sample
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=87vansrfjb.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=guix-devel@gnu.org \
--cc=samplet@ngyro.com \
/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.