From: znavko@disroot.org
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>, guix-devel@gnu.org
Subject: Re: Is there a way to upgrade only packages with substitutes?
Date: Sat, 03 Aug 2019 04:30:56 +0000 [thread overview]
Message-ID: <30697aebc00280145b4769566fc9103d@disroot.org> (raw)
In-Reply-To: <871ry38fl9.fsf@gmail.com>
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?).
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.
August 2, 2019 8:42 PM, "Katherine Cox-Buday" <cox.katherine.e@gmail.com> wrote:
> Hey Guix!
>
> Very often I find myself updating systems only to get stuck on building
> something large like LibreOffice or Un-Googled Chromium. Usually the
> substitutes for these are available a few days later.
>
> It would be nice if I could pass a flag to `guix package -u` that would
> disallow building in the event a substitute wasn't available. Is that
> `--fallback=false`? If so, that's a double-negative; is there a clearer
> way to represent both without acreting options?
>
> --
> Katherine
next prev parent reply other threads:[~2019-08-03 4:31 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 [this message]
2019-08-03 13:25 ` Katherine Cox-Buday
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=30697aebc00280145b4769566fc9103d@disroot.org \
--to=znavko@disroot.org \
--cc=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.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).