From 52ef5711dcd189d8f45555490aabf2c6958df6ed Mon Sep 17 00:00:00 2001 From: Rasmus Villemoes Date: Fri, 26 Aug 2022 14:20:44 +0200 Subject: bitbake.conf: set BB_DEFAULT_UMASK using ??= Currently, there's no way for the user's site.conf, local.conf or similar to set BB_DEFAULT_UMASK, because those files are included by bitbake.conf prior to the unconditional assignment of BB_DEFAULT_UMASK. To make that possible, use a weak default assignment instead. This is also consistent with most other variable assignments in the lower half of bitbake.conf. I believe the risk of a regression is very small; it would require something like somebody having a definition of BB_DEFAULT_UMASK in a local configuration file, and having been relying on that _not_ taking effect. (From OE-Core rev: e3dbded499f0bd1e71abb0650ae98fd9ade94250) Signed-off-by: Rasmus Villemoes Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie --- 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 dd2df8a552..52a36d788b 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf @@ -928,7 +928,7 @@ SHELL[unexport] = "1" TRANSLATED_TARGET_ARCH ??= "${@d.getVar('TARGET_ARCH').replace("_", "-")}" # Set a default umask to use for tasks for determinism -BB_DEFAULT_UMASK = "022" +BB_DEFAULT_UMASK ??= "022" # Complete output from bitbake BB_CONSOLELOG ?= "${LOG_DIR}/cooker/${MACHINE}/${DATETIME}.log" -- cgit v1.2.3-54-g00ecf