unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: znavko@disroot.org
Cc: guix-devel@gnu.org
Subject: Re: Is there a way to upgrade only packages with substitutes?
Date: Sat, 03 Aug 2019 08:25:02 -0500	[thread overview]
Message-ID: <87wofu755d.fsf@gmail.com> (raw)
In-Reply-To: <30697aebc00280145b4769566fc9103d@disroot.org> (znavko@disroot.org's message of "Sat, 03 Aug 2019 04:30:56 +0000")

znavko@disroot.org writes:

> Hello, Katherine! I fuzzily remember this subject in maillists, maybe
> we discussed this feature. And there were instruction of how to define
> in `guix package -u` those packages you won't update.
> Also I know guix has feature to check substitutes (`guix weather`, is
> it?).

Yes, sorry, I think I have given the impression that I have had no way
of working around this; I do, and I have. It is just an inconvenience.

Usually what I do is that when I come upon a package that will take a
long time to build, I kill the upgrade, pass the package to
`--do-not-upgrade`, and continue.

> I think we need a script that will do this:
> 1) guix pull
> 2) get a list of new packages and dependencies that all will be updated
> 3) check which of them haven't substitutes
> 4) run `guix package -u` without those packages that have not substitutes.
> 4.1) or run `guix package -u` without only those big packages you
> defined like 'not to update if they have no substitutes'
>
> I think this can be done with guix features but this is hard work, not
> for usual users.
> And sure guix must have this feature.

Yes, I think it would be better for users, and on Guix's infrastructure.

-- 
Katherine

  reply	other threads:[~2019-08-03 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 20:41 Is there a way to upgrade only packages with substitutes? Katherine Cox-Buday
2019-08-03  0:03 ` Alex Vong
2019-08-03  4:30 ` znavko
2019-08-03 13:25   ` Katherine Cox-Buday [this message]
2019-08-04  0:19   ` L p R n d n
2019-08-04  6:40   ` znavko
2019-08-04 21:18     ` P
  -- strict thread matches above, loose matches on Subject: below --
2019-08-03 22:11 Alex Vong

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=87wofu755d.fsf@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=znavko@disroot.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 public inbox

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

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).