From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] sbuild: Fix low hit ratio for ccache on linux kernel rebuild
Date: Fri, 15 Jul 2022 15:50:15 +0200 [thread overview]
Message-ID: <YtFwl3QBLXdTqVtg@ilbers.de> (raw)
In-Reply-To: <25512947.1r3eYUQgxm@home>
On Fri, Jul 15, 2022 at 04:44:29PM +0300, Uladzimir Bely wrote:
> It can be moved to the kernel recipe, but you left me a bit confused. Why
> changing of build directory from some random (from build to build) path to
> some fixed one (the same hash on every rebuild) makes the build less
> reproducible?
Debian wants to have identical binary package contents from different builds,
see https://wiki.debian.org/ReproducibleBuilds. I don't know by heart whether /
how that works for debug info, though. Seems that at least absolute paths
should be a no-go.
With kind regards,
Baurzhan
next prev parent reply other threads:[~2022-07-15 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 11:27 Uladzimir Bely
2022-07-15 13:27 ` Moessbauer, Felix
2022-07-15 13:44 ` Uladzimir Bely
2022-07-15 13:50 ` Baurzhan Ismagulov [this message]
2022-07-15 14:48 ` Moessbauer, Felix
2022-07-15 13:47 ` Baurzhan Ismagulov
2022-07-17 18:53 ` Jan Kiszka
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=YtFwl3QBLXdTqVtg@ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox