From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "chris.laplante@agilent.com" <chris.laplante@agilent.com>,
"Openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Strange behavior in sstate-diff-machines.sh
Date: Mon, 03 Feb 2025 22:29:10 +0000 [thread overview]
Message-ID: <5908461b69f26ee1598359ddadc15e58a9049ccb.camel@linuxfoundation.org> (raw)
In-Reply-To: <DM8PR12MB54300A067D077BCEED12ADF58BF52@DM8PR12MB5430.namprd12.prod.outlook.com>
On Mon, 2025-02-03 at 22:19 +0000, chris.laplante@agilent.com wrote:
> > I've never liked that script and personally, I've always wanted to
> > make bitbake's
> > owm signature "diff" as helpful as we can. There are ton of
> > different things
> > that conspire against us in doing that and whilst we've improved,
> > it still isn't
> > ideal.
> >
> > I'd note that the script predates hash equivalence and that can be
> > a big factor
> > in things things like this. We've struggled to reconcile some of
> > the tools with
> > changes like hash equivalence :(
> >
> > So yes, I can imagine do_package matching between the two machines,
> > then
> > hashequiv would reuse the later tasks like do_package_write_rpm
> > from sstate.
>
> Thanks for the info.
>
> Would this be the kind of thing that is best ported to bitbake-
> diffsigs, maybe as some kind of recursive mode? (Just asking out of
> curiosity - I don't yet have a strong enough grasp of all the
> caching/signature stuff)
>
> For posterity, I hacked up the script with this patch and it fixed my
> issue (whilst probably introducing other, subtler issues).
I'm not sure what the best thing to do is. The script can make some
assumptions that bitbake can't and does in some ways have more data so
it may not be possible but I've not looked at this area in a while...
Cheers,
Richard
next prev parent reply other threads:[~2025-02-03 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 21:34 Strange behavior in sstate-diff-machines.sh chris.laplante
2025-02-03 22:10 ` [OE-core] " Richard Purdie
2025-02-03 22:19 ` chris.laplante
2025-02-03 22:29 ` Richard Purdie [this message]
2025-02-04 11:25 ` Alexander Kanavin
2025-02-04 14:13 ` chris.laplante
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=5908461b69f26ee1598359ddadc15e58a9049ccb.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=chris.laplante@agilent.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