unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tirifto <tirifto@posteo.cz>
To: help-guix@gnu.org
Subject: Re: How to check Guix servers have Ungoogled-Chrome substitutions for me?
Date: Sat, 27 Feb 2021 20:17:44 +0100	[thread overview]
Message-ID: <20210227201744.50d511ce@posteo.cz> (raw)
In-Reply-To: <44bfc5aa7479b0f97d93965fe8fa2dbf@disroot.org>

Le Sat, 27 Feb 2021 17:14:19 +0000,
znavko--- via <help-guix@gnu.org> a écrit :

> Hello, Guix Help!

Hello!

> I often run `guix pull && guix package -u` and sometimes it tooks too
> much time, and my fan is noisy because some heavy package (like
> Icecat or Ungoogled-Chromium or LibreOffice0 is compiling from
> sources.
> 
> It's a pity, because to get the newest version of such is not
> included into my wish list, and I waste time.
> 
> Is there some 'guix' command run that will download updates and will
> check which packages are to be substitued, and which are to be
> compiled?
> 
> I want to see this. And then I want to solve to prevent compilation
> of LibreOffice, Chromium, Icecat if they are to be compiled.
> 
> Please, show me this hack.

You can run ‘guix weather [package-name-1] [package-name-2] […]’ to see
if substitutes are available for any given set of packages. I do this
for packages that I know are going to get upgraded and would take a
long time to build on my system. But chances are that the solutions
other have posted can already do this better for you.

Best of wishes
// Tirifto


  parent reply	other threads:[~2021-02-27 19:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27 17:14 How to check Guix servers have Ungoogled-Chrome substitutions for me? znavko--- via
2021-02-27 18:06 ` Vincent Legoll
2021-02-27 18:13 ` Andreas Enge
2021-02-27 19:17 ` Tirifto [this message]
2021-02-27 19:31 ` Wiktor Żelazny
2021-03-01  9:58 ` zimoun

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=20210227201744.50d511ce@posteo.cz \
    --to=tirifto@posteo.cz \
    --cc=help-guix@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.
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).