Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: RFC: Check for reproducible builds.
Date: Fri, 30 Apr 2021 19:45:55 +0200	[thread overview]
Message-ID: <20210430174555.6PetZ4wKrAgJpecAbSuINsr4H7d5GDWY-jAZqLxe1QU@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: 1417 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/30588#issuecomment-830256754

Comment:
So, thinking about this.

- the current version of this PR won't almost ever have matched checksums, because of `source-revisions`; we would have to work around that if we want to go with this path
- very few people build packages locally with debug symbols, and `compile with debug + strip` is different from `compile without debug`, so anyone updating templates will need to consider it
- void doesn't have a package archive, nor do we have `BUILDINFO`. While `source-revisions` provides the git repo state (hooks and build styles), and, therefore, the version of all the packages listed in the template in `(host)makedepends`, it doesn't record the version of the dependencies of the packages listed in `(host)makedepends`. Specifying a `BUILDINFO` file to record that information would be necessary. The archive would be necessary to have somewhere to fetch the specific versions of packages from

The current vision of `reproducible-builds` usually means trying to have the same build environment to see if the package is deterministic. If we want to study what packages are "reproducible" when built with different dependencies and etc (remembering that even line numbers in headers can change debug info), I think we would have to call this effort something else.

  parent reply	other threads:[~2021-04-30 17:45 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
2021-04-30 15:55 ` ericonr
2021-04-30 16:59 ` Chocimier
2021-04-30 17:18 ` ericonr
2021-04-30 17:45 ` ericonr [this message]
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=20210430174555.6PetZ4wKrAgJpecAbSuINsr4H7d5GDWY-jAZqLxe1QU@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).