all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: L  p R n  d n    <guix@lprndn.info>
To: sirmacik <sirmacik@wioo.waw.pl>
Cc: Raghav Gururajan <raghavgururajan@disroot.org>, help-guix@gnu.org
Subject: Re: Doubt regarding waiting for substitutes
Date: Mon, 30 Sep 2019 10:57:13 +0200	[thread overview]
Message-ID: <878sq6qhzq.fsf@lprndn.info> (raw)
In-Reply-To: <87wodqg0dr.fsf@wioo.waw.pl> (sirmacik@wioo.waw.pl's message of "Mon, 30 Sep 2019 01:15:28 +0200")

Hello,

sirmacik <sirmacik@wioo.waw.pl> writes:

> 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. (; 
>

Not a rule of thumb or anything, just sharing my way.
As I don't need any specific update or commits I usually use just `guix pull
commit=...` to update and pick a commit from around 24h ago. Unless
there has been significant changes I end up building very few packages
if any at all. (not using ungoogled-chromium)

> --
> Cheers,
> sirmacik
> PGP: 0xE0DC81D523891771


Hope it helps,

L  p R n  d n

      reply	other threads:[~2019-09-30  8:57 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
2019-09-30  8:57   ` L p R n d n [this message]

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=878sq6qhzq.fsf@lprndn.info \
    --to=guix@lprndn.info \
    --cc=help-guix@gnu.org \
    --cc=raghavgururajan@disroot.org \
    --cc=sirmacik@wioo.waw.pl \
    /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.