From: zimoun <zimon.toutoune@gmail.com>
To: Adam Faiz <adam.faiz@disroot.org>, atai@atai.org
Cc: help-guix@gnu.org
Subject: Re: guix package build: can distcc be used?
Date: Fri, 06 Jan 2023 17:12:01 +0100 [thread overview]
Message-ID: <87zgavhcby.fsf@gmail.com> (raw)
In-Reply-To: <6044245d-5533-4994-9316-d6a227e67e3d@disroot.org>
Hi,
On Sun, 25 Dec 2022 at 18:21, Adam Faiz <adam.faiz@disroot.org> wrote:
> It's unknown whether implementing usage of distcc and enabling it in
> `guix build` will affect bit-for-bit reproducibility of packages.
The question is how isolated the distributed computational environments
are.
> The distcc feature request and adding distcc to guix's dependency
> closure and should be discussed further on guix-devel before implementing.
Personally, I am missing what distcc brings compared to the current
Guix offload mechanism. Could you (distcc user) elaborate?
Cheers,
simon
next prev parent reply other threads:[~2023-01-06 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 10:21 guix package build: can distcc be used? Adam Faiz
2023-01-06 16:12 ` zimoun [this message]
2023-01-06 18:48 ` Vagrant Cascadian
2023-01-09 11:16 ` Simon Tournier
-- strict thread matches above, loose matches on Subject: below --
2022-12-24 9:33 Andy Tai
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=87zgavhcby.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=adam.faiz@disroot.org \
--cc=atai@atai.org \
--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).