[PATCH 1/1] exclude UNSHARE_SUBUID_BASE from cache signatures

[Felix Moessbauer]

Similar to the exclusion of RUN_PRIVILEGED_CMD in 2dae8b5ca, this
variable contains host-specific subid ranges, but functionally it
does not matter how privileged mode is entered: The outputs must be
identical in unshare and schroot mode when using the command.

By that, we can safely exclude it from the cache signatures.

Signed-off-by: Felix Moessbauer <felix.mo...@siemens.com>
---
meta/conf/bitbake.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 7a12a3ef..e69ec3bb 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -100,7 +100,7 @@ REPO_BASE_DB_DIR = "${DEPLOY_DIR}/base-apt/${DISTRO}/db"
# Setup our default hash policy
BB_SIGNATURE_HANDLER ?= "OEBasicHash"
BB_HASHEXCLUDE_ISAR ?= "CCACHE_DEBUG LAYERDIR_core SCRIPTSDIR TOPDIR ISAR_BUILD_UUID \
- RUN_PRIVILEGED_CMD"
+ RUN_PRIVILEGED_CMD UNSHARE_SUBUID_BASE"
BB_HASHEXCLUDE_COMMON ?= "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH BBSERVER DL_DIR \
THISDIR FILESEXTRAPATHS FILE_DIRNAME HOME LOGNAME SHELL \
USER FILESPATH STAGING_DIR_HOST STAGING_DIR_TARGET COREBASE PRSERV_HOST \
--
2.55.0

[Zhihang Wei]

Applied to next, thanks.

Zhihang