From: Maxime Devos <maximedevos@telenet.be>
To: Giovanni Biscuolo <g@xelera.eu>,
Ricardo Wurmus <rekado@elephly.net>,
guix-devel@gnu.org
Cc: Arun Isaac <arunisaac@systemreboot.net>
Subject: Re: On commit access, patch review, and remaining healthy
Date: Sun, 12 Jun 2022 15:10:35 +0200 [thread overview]
Message-ID: <225108d8b5a3c5e900009b38d65137ff3915d9ed.camel@telenet.be> (raw)
In-Reply-To: <874k0qi5g1.fsf@xelera.eu>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Giovanni Biscuolo schreef op zo 12-06-2022 om 11:42 [+0200]:
> > or have packages with bundled dependencies (e.g. vendored jars).
>
> bundling binaries it's (is it?) for sure against the definition of a
> reproducible build, but what about bundling (source) dependencies?
>
> AFAIU not to bundle (source) dependencies is an additional Guix
> requirement (and it is a Good Thing™): do I miss something?
FWIW, sometimes the bundled ‘source’ dependencies contain bundled
binaries of their own. So while AFAICT not strictly necessary for
reproducible builds, unbundling ‘source dependencies’ makes ensuring
reproducibility(*) much more convenient.
(*) i.e., the non-trivial kind of reproducibility, where things are
actually built from source instead of copying binaries.
> honestly I did not study all the reproducible-builds.org
> documentation,
> but it's impossible to me to understand how a packaged upstream jar
> can be considered reproducible (and bootstrappable); maybe distros
> like NixOS are still slowly transitioning to a full reproducible
> build workflow?
It's ‘reproducible’ in the trivial sense that you can ‘reproduce’ a
scientific paper by putting it a photocopier. That way, you can
reproduce the results, but you cannot confirm whether these results
were correct.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-12 13:11 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12124.1654864076.1231.guix-devel@gnu.org>
2022-06-12 8:18 ` On commit access, patch review, and remaining healthy Ricardo Wurmus
2022-06-12 9:42 ` Giovanni Biscuolo
2022-06-12 13:10 ` Maxime Devos [this message]
2022-06-13 9:34 ` Giovanni Biscuolo
2022-06-13 10:48 ` Maxime Devos
2022-06-13 14:21 ` Giovanni Biscuolo
2022-06-14 10:51 ` «Reproducibility vs. Replicability: A Brief History of a Confused Terminology» zimoun
2022-06-12 8:21 ` On commit access, patch review, and remaining healthy Ricardo Wurmus
2022-06-02 15:10 Ludovic Courtès
2022-06-02 20:22 ` Brian Cully via Development of GNU Guix and the GNU System distribution.
2022-06-03 19:37 ` Ludovic Courtès
2022-06-03 21:17 ` Ricardo Wurmus
2022-06-07 7:08 ` Efraim Flashner
2022-06-07 15:11 ` Ludovic Courtès
2022-06-08 11:39 ` Efraim Flashner
2022-06-08 21:10 ` Ludovic Courtès
2022-06-20 12:53 ` Hartmut Goebel
2022-06-21 15:44 ` zimoun
2022-06-22 9:19 ` Munyoki Kilyungi
2022-06-02 20:32 ` Pier-Hugues Pellerin
2022-06-03 19:42 ` Ludovic Courtès
2022-06-02 21:35 ` Luis Felipe
2022-06-06 12:11 ` Arun Isaac
2022-06-06 21:43 ` Ludovic Courtès
2022-06-07 6:44 ` zimoun
2022-06-08 9:30 ` Giovanni Biscuolo
2022-06-14 12:24 ` zimoun
2022-06-15 7:01 ` Arun Isaac
2022-06-15 9:19 ` Ludovic Courtès
2022-06-19 6:55 ` Paul Jewell
2022-06-20 12:11 ` Arun Isaac
2022-06-15 15:11 ` Giovanni Biscuolo
2022-06-08 10:54 ` Giovanni Biscuolo
2022-06-09 19:55 ` Arun Isaac
2022-06-08 9:49 ` Giovanni Biscuolo
2022-06-09 19:50 ` Arun Isaac
2022-06-10 12:27 ` Giovanni Biscuolo
2022-06-10 15:03 ` Efraim Flashner
2022-06-10 16:10 ` Giovanni Biscuolo
2022-06-10 16:26 ` Giovanni Biscuolo
2022-06-10 15:03 ` Maxime Devos
2022-06-11 4:13 ` Thiago Jung Bauermann
2022-06-11 9:37 ` Ludovic Courtès
2022-06-14 11:54 ` zimoun
2022-06-14 15:54 ` Maxim Cournoyer
2022-06-15 6:46 ` Arun Isaac
2022-06-13 12:19 ` Arun Isaac
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=225108d8b5a3c5e900009b38d65137ff3915d9ed.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=arunisaac@systemreboot.net \
--cc=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).