From: ludo@gnu.org (Ludovic Courtès)
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org, 783210@bugs.debian.org,
Aurelien Jarno <aurelien@aurel32.net>,
Ximin Luo <infinity0@debian.org>
Subject: Re: [PATCH] nscd_stat.c: make the build reproducible
Date: Fri, 29 Jul 2016 13:30:00 -0000 [thread overview]
Message-ID: <877fc4d5n6.fsf@gnu.org> (raw)
In-Reply-To: <dfc1aba1-1788-6b73-602e-3ffd6936c14d@redhat.com> (Florian Weimer's message of "Thu, 28 Jul 2016 15:15:08 -0400")
Florian Weimer <fweimer@redhat.com> skribis:
> We still need the time-based approach if the build ID is not
> available, but I expect most distributions will have something like
> it.
FWIW in Guix we solve it by filling the ‘compilation’ array with a
substring of the installation prefix¹.
Since the installation prefix is something like
/gnu/store/5fx3vscv9pqjr1k0vyaqnpqlvvzl8rff-glibc-2.22, which comprises
a hash of all the source, build scripts, and dependencies used to build
it, we know that it uniquely identifies the result of this specific
glibc build.
The build ID should be a good approximation of this.
Ludo’.
¹ http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/base.scm#n603
next prev parent reply other threads:[~2016-07-29 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 17:06 Aurelien Jarno
2016-03-08 23:37 ` Mike Frysinger
2016-03-09 7:54 ` Aurelien Jarno
2016-03-09 22:30 ` Mike Frysinger
2016-07-28 19:33 ` Florian Weimer
2016-07-29 13:30 ` Ludovic Courtès [this message]
2016-08-01 4:52 ` Mike Frysinger
2016-11-04 17:54 ` Ximin Luo
2016-11-04 18:14 ` Ximin Luo
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=877fc4d5n6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=783210@bugs.debian.org \
--cc=aurelien@aurel32.net \
--cc=fweimer@redhat.com \
--cc=infinity0@debian.org \
--cc=libc-alpha@sourceware.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).