From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: RFC: Check for reproducible builds.
Date: Fri, 30 Apr 2021 15:01:52 +0200 [thread overview]
Message-ID: <20210430130152.0NhUDVLp0UNhhbJQdnDuRnLldmSSXP6sBrvRo3eac5c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30588@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30588#issuecomment-830079060
Comment:
To explain my comment above, tracking `source-revisions` is equivalent to `.BUILDINFO` files used by other distros (which can be necessary because they don't use monorepos and so the build environment is much more variable), and so I'm strongly against its removal.
IIRC there was some discussion about whether a `.BUILDINFO` file should be included in the package itself or be a "side cart" file, but that adds complexity, more files to sign and track, and removes what is currently built-in information that can be useful for someone to try and reproduce things locally (without having to download the side cart with a weird path).
next prev parent reply other threads:[~2021-04-30 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 8:18 [PR PATCH] " Gottox
2021-04-30 12:53 ` [PR REVIEW] " ericonr
2021-04-30 13:01 ` ericonr [this message]
2021-04-30 15:55 ` ericonr
2021-04-30 16:59 ` Chocimier
2021-04-30 17:18 ` ericonr
2021-04-30 17:45 ` ericonr
2021-04-30 23:56 ` Gottox
2021-05-01 0:00 ` Gottox
2021-05-01 0:57 ` ericonr
2021-05-01 1:01 ` ericonr
2021-05-21 13:49 ` [PR PATCH] [Closed]: " Gottox
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210430130152.0NhUDVLp0UNhhbJQdnDuRnLldmSSXP6sBrvRo3eac5c@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).