unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: cox.katherine.e@gmail.com, guix-devel@gnu.org
Subject: Re: Is there a way to upgrade only packages with substitutes?
Date: Sun, 04 Aug 2019 06:11:33 +0800	[thread overview]
Message-ID: <86lfw9kiga.fsf@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]

[Forget to reply to OP, resending ...]

Hello Katherine,

Katherine Cox-Buday writes:

> 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?

I don't think there is an option for this. It would certainly be helpful
if there were one.

Currently, my workaround is to create a manifest listing packages to be
installed:
https://notabug.org/alexvong1995/guix-package-declaration/src/master/manifest
and run "guix package -m ./manifest" instead of "guix package -u".

[emacs-guix users can run the interactive function `guix-apply-manifest'
instead.]

When there is a package without substitutes, I will stop the command,
comment out the said package and re-run the command. I will also re-try
after a few days when more substitutes are available.

Hope this help!

Cheers,
Alex

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

             reply	other threads:[~2019-08-03 22:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03 22:11 Alex Vong [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2019-08-04  0:19   ` L p R n d n
2019-08-04  6:40   ` znavko
2019-08-04 21:18     ` P

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=86lfw9kiga.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --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).