public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Pedro Ferreira" <pedro.silva.ferreira@criticaltechworks.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] buildhistory.bbclass: restore BUILDHISTORY_PRESERVE files
Date: Thu, 06 Mar 2025 06:26:34 -0800	[thread overview]
Message-ID: <359.1741271194425273451@lists.openembedded.org> (raw)
In-Reply-To: <16166.1737643041567770551@lists.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 613 bytes --]

Simple scenario to test it:

*Pre-conditions:*
INHERIT += "buildhistory"
BUILDHISTORY_RESET = "1"
BUILDHISTORY_PRESERVE:append = " files-in-package.txt"

*Run:*
bitbake -c cleansstate base-passwd && bitbake base-passwd
*Check:*
cat PATH_TO_BUILD_dir/buildhistory/packages/core2-64-poky-linux/base-passwd/base-passwd-dbg/files-in-package.txt
(File exists and content ok)
*Run:*
rm -rf tmp && bitbake base-passwd (it will use sstate cache)
*Check:*
cat PATH_TO_BUILD_dir/buildhistory/packages/core2-64-poky-linux/base-passwd/base-passwd-dbg/files-in-package.txt
(File wont exist)

Cheers,
Pedro

[-- Attachment #2: Type: text/html, Size: 924 bytes --]

  reply	other threads:[~2025-03-06 14:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15 15:31 [PATCH] buildhistory.bbclass: restore BUILDHISTORY_PRESERVE files Pedro Ferreira
2025-01-22 13:42 ` [OE-core] " Ross Burton
2025-01-23 14:37   ` Pedro Ferreira
2025-03-06 14:26     ` Pedro Ferreira [this message]
2025-03-12 13:40       ` [OE-core] " Ross Burton
2025-06-23 20:48 ` Richard Purdie
2025-06-25 10:26   ` Fabio Berton
2025-06-25 10:46     ` 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=359.1741271194425273451@lists.openembedded.org \
    --to=pedro.silva.ferreira@criticaltechworks.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