Openembedded Core Discussions
 help / color / mirror / Atom feed
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:24:25 +0100	[thread overview]
Message-ID: <bff014f2950bfbd1f3027a85992eb7c0f4e108b4.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-L2P96Ev=xbr5LWoL7OvyVU6hGkCajksgMgxPNF4ZQ2w@mail.gmail.com>

On Thu, 2023-08-10 at 17:27 +0200, Alexander Kanavin wrote:
> On Thu 10. Aug 2023 at 17.10, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Thu, 2023-08-10 at 16:57 +0200, Alexander Kanavin wrote:
> > > I don’t follow i am afraid. How would having separate usr expose
> > > issues that merged usr would hide?
> > 
> > Most host systems are moving over to merged usr. If host paths to a
> > binary were to creep in (e.g. the path to a tool, /usr/bin/xxx),
> > our
> > non usrmerge config would be more likely to generate a
> > reproducibility
> > mismatch than one with usrmerge enabled.
> 
> But then it would creep into both build A and build B since both
> would come from the same host or two hosts both with usrmerge, and
> there would be no mismatch. No?

True, I'm thinking of something slightly different.

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.

Cheers,

Richard


  reply	other threads:[~2023-08-10 16:24 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 [this message]
2023-08-10 16:32         ` Alexander Kanavin
2023-08-10 16:39           ` Richard Purdie

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=bff014f2950bfbd1f3027a85992eb7c0f4e108b4.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