From: sirmacik <sirmacik@wioo.waw.pl>
To: Raghav Gururajan <raghavgururajan@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Doubt regarding waiting for substitutes
Date: Mon, 30 Sep 2019 01:15:28 +0200 [thread overview]
Message-ID: <87wodqg0dr.fsf@wioo.waw.pl> (raw)
In-Reply-To: <c999964f50792358363e176aa905469678a07439.camel@disroot.org> (Raghav Gururajan's message of "Thu, 26 Sep 2019 03:23:30 -0400")
Raghav Gururajan <raghavgururajan@disroot.org> writes:
> Hello Guix!
>
> After `guix pull`, I usually run `guix upgrade --dry-run` to check
> which derivations will be built. If I find heavy ones like icecat,
> evolution, calibre, kodi, qtwebkit etc., what is the general rule of
> thumb waiting period for the substitutes to be available for those
> packages, before I re-run `guix upgrade`? Assuming I will not be doing
> another `guix pull` during the waiting.
Hey Guix!
I'd like to bump the question. New packages like icecat and
ungoogled-chromium take sometimes really long time to come up.
Trying to compile those has even made fan in my laptop creak. (;
--
Cheers,
sirmacik
PGP: 0xE0DC81D523891771
next prev parent reply other threads:[~2019-09-29 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 7:23 Doubt regarding waiting for substitutes Raghav Gururajan
2019-09-29 23:15 ` sirmacik [this message]
2019-09-30 8:57 ` L p R n d n
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=87wodqg0dr.fsf@wioo.waw.pl \
--to=sirmacik@wioo.waw.pl \
--cc=help-guix@gnu.org \
--cc=raghavgururajan@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.
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).