From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] selftest/reproducible: Update config to match ongoing changes
Date: Thu, 10 Aug 2023 17:39:40 +0100 [thread overview]
Message-ID: <4dac2eacd924bd5f422abd37f29b3ede94c6bdda.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8oojCWS-rV0tOfOGYN4fCqAAX793U0nbX_y1ZSOk3ohQ@mail.gmail.com>
On Thu, 2023-08-10 at 18:32 +0200, Alexander Kanavin wrote:
> On Thu, 10 Aug 2023 at 18:24, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > I'm thinking having usrmerge disabled makes it more likely we'd notice
> > a "bad" tool path creeping into builds rather than the case where the
> > host and target share the same paths. That isn't a reproducibility
> > case, more a general one.
>
> But then should we really drop usrmerge/systemd from reproducibility
> as the bad path wouldn't be noticed until runtime (or maybe in
> package_qa), and that is tested elsewhere?
We do build systemd configurations in multiple places and package_qa
checks are run.
> FWIW, I'm not particularly happy that systemd is nowadays de facto
> dictating filesystem layouts. Or that you can use any libc you like,
> as long as it's glibc. And that all/most key developers are employed
> by Microsoft. Monocultures are not good, even if source code is
> available.
I am also a bit worried about that and I don't really want to tie
ourselves to that in our test matrix.
Whilst removing systemd from there looks fairly drastic, it isn't as
bad as it seems. From the reproducibility work, we've now much tighter
QA checks in general so the reprodcubility issues appearing now are
much reduced and usually toolchain level rather than random path issues
which the QA checks now find much earlier. As such, I doubt overall
reproducibility will suffer regressions.
Cheers,
Richard
prev parent reply other threads:[~2023-08-10 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 13:34 [PATCH] selftest/reproducible: Update config to match ongoing changes Richard Purdie
2023-08-10 14:57 ` [OE-core] " Alexander Kanavin
2023-08-10 15:10 ` Richard Purdie
2023-08-10 15:27 ` Alexander Kanavin
2023-08-10 16:24 ` Richard Purdie
2023-08-10 16:32 ` Alexander Kanavin
2023-08-10 16:39 ` Richard Purdie [this message]
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=4dac2eacd924bd5f422abd37f29b3ede94c6bdda.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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