From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 43843@debbugs.gnu.org
Subject: bug#43843: git-annex is not Reproducible
Date: Tue, 13 Oct 2020 15:05:59 +0200 [thread overview]
Message-ID: <87tuuyjmx4.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ2KwAFTKGpWMO+rophDg1bAsa_dYNaEYcmMQa_ATcNmUw@mail.gmail.com> (zimoun's message of "Mon, 12 Oct 2020 13:55:59 +0200")
zimoun <zimon.toutoune@gmail.com> skribis:
> On Mon, 12 Oct 2020 at 12:34, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> > Does the parallel build save a lot of time and CPU? If yes, maybe we
>> > could to provide a transformation for the expert, something like
>> > "haskell-build-system-with-parellel-build" which tweaks
>> > "PARALLEL-BUILD?", similarly to the recent "no tests". WDYT?
>>
>> We shouldn’t compromise reproducibility for parallel builds. Ideally we
>> would figure out what exactly causes the differences and fix that
>> instead of disabling parallel builds, but if that turns out to be too
>> difficult I think we should just revert this until we have a good fix.
>>
>> Perhaps something can be done by fixing the order of files somewhere.
>
> My proposal is for the expert and not at the CLI level. Something
> like "(funky-name ghc-foo)" which returns a new package with
> PARALLEL-BUILD? turned to #t. And the default should be #f. WDYT?
You can always build with ‘--cores=1’, which will ensure both the build
and test will run sequentially.
Ludo’.
next prev parent reply other threads:[~2020-10-13 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 10:35 bug#43843: git-annex is not Reproducible zimoun
2020-10-08 3:04 ` Kyle Meyer
2020-10-08 6:17 ` Efraim Flashner
2020-10-09 20:33 ` zimoun
2020-10-10 9:35 ` Ricardo Wurmus
2020-10-12 9:31 ` zimoun
2020-10-12 10:36 ` Ricardo Wurmus
2020-10-12 11:55 ` zimoun
2020-10-13 13:05 ` Ludovic Courtès [this message]
2020-10-13 13:28 ` 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=87tuuyjmx4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43843@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).