unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Matthew Brooks <matthewfbrooks@mailbox.org>,
	"help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Avoiding rebuilds (e.g. of mariadb, the entire Rust chain, etc.)?
Date: Wed, 29 Dec 2021 10:26:34 +0100	[thread overview]
Message-ID: <86k0fnkbhx.fsf@gmail.com> (raw)
In-Reply-To: <20211226234130.5ad3d9f2@mailbox.org>

Hi,

On Sun, 26 Dec 2021 at 23:41, Matthew Brooks <matthewfbrooks@mailbox.org> wrote:

> I've got substitutes turned off (primarily because I like the idea of
> every package being "home built" as it were), but I can't imagine that
> even the official substitiute servers would be able to keep up with
> the constant rebuilds my system seems to want unless I've got
> something horribly misconfigured somewhere. 

The only “home built” are the “tunable“ [1] packages, which are very
rare.  Otherwise, Guix tries very hard to build portable packages [2].

Personally, I see only 2 cases to have substitutes turned off:

  1) you often challenge your builds against substitutes ones and report
     reproducibility or performances issues,
  2) you inspect all the sources for trusting them before building.

If not, for what my opinion is worth, I do not understand the aim for
burning such energy in this world of climate change.

1: <https://issues.guix.gnu.org/52283#27>
2:<https://hpc.guix.info/blog/2018/01/pre-built-binaries-vs-performance/>


Cheers,
simon


      parent reply	other threads:[~2021-12-29  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27  5:41 Avoiding rebuilds (e.g. of mariadb, the entire Rust chain, etc.)? Matthew Brooks
2021-12-27  9:23 ` David Lecompte via
2021-12-29  9:12   ` zimoun
2022-01-02 17:36     ` David Lecompte
2022-01-03 16:42       ` zimoun
2021-12-28  0:13 ` Leo Famulari
2021-12-29  9:26 ` zimoun [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

  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=86k0fnkbhx.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=matthewfbrooks@mailbox.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).