public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 3/7] signatures: exclude BITBAKEDIR from WIC
Date: Wed,  4 May 2022 13:41:05 +0200	[thread overview]
Message-ID: <20220504114109.3411005-4-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20220504114109.3411005-1-felix.moessbauer@siemens.com>

This patch excludes the absolute BITBAKEDIR from the variables
that are used to compute the signature for wic tasks.
As bitbake is shipped with the CORE layer repo, no changes are
expected and have to be tracked.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/classes/imagetypes_wic.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/imagetypes_wic.bbclass b/meta/classes/imagetypes_wic.bbclass
index cfcc94c7..db7bbe71 100644
--- a/meta/classes/imagetypes_wic.bbclass
+++ b/meta/classes/imagetypes_wic.bbclass
@@ -147,6 +147,7 @@ IMAGE_CMD_wic() {
     check_for_wic_warnings
 }
 
+wic_do_mounts[vardepsexclude] += "BITBAKEDIR"
 wic_do_mounts() {
     buildchroot_do_mounts
     sudo -s <<'EOSUDO'
@@ -162,6 +163,7 @@ wic_do_mounts() {
 EOSUDO
 }
 
+generate_wic_image[vardepsexclude] += "BITBAKEDIR"
 generate_wic_image() {
     export FAKEROOTCMD=${FAKEROOTCMD}
     export BUILDDIR=${BUILDDIR}
-- 
2.30.2


  parent reply	other threads:[~2022-05-04 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 11:41 [PATCH 0/7] Further improve cachability of ISAR Felix Moessbauer
2022-05-04 11:41 ` [PATCH 1/7] signatures: exclude path to core layer from bb hashes Felix Moessbauer
2022-05-04 11:41 ` [PATCH 2/7] signatures: whitelist external SCRIPTSDIR Felix Moessbauer
2022-05-04 11:41 ` Felix Moessbauer [this message]
2022-05-04 11:41 ` [PATCH 4/7] signatures: use TOPDIR instead of BUILDDIR in wic Felix Moessbauer
2022-05-04 11:41 ` [PATCH 5/7] signatures: unify WKS_* variable exclusions with OE Felix Moessbauer
2022-05-04 11:41 ` [PATCH 6/7] signatures: exclude TOPDIR from signatures Felix Moessbauer
2022-05-04 11:41 ` [PATCH 7/7] signatures: do not expand SRC_URI Felix Moessbauer
2022-05-16  9:29 ` [PATCH 0/7] Further improve cachability of ISAR Anton Mikanovich

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=20220504114109.3411005-4-felix.moessbauer@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --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