diff options
| author | Rasmus Villemoes <rasmus.villemoes@prevas.dk> | 2022-08-26 14:20:44 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-09-12 08:41:47 +0100 |
| commit | bdc6dfc12fc11ba4af84afe5134f068ea099f233 (patch) | |
| tree | cbcff4efdb822923b2c1a427ac9a7877864a2f97 /bitbake/lib/bb/parse/parse_py | |
| parent | 2723b8dae83b78ecca6f71d76cabf6107f1581ca (diff) | |
| download | poky-bdc6dfc12fc11ba4af84afe5134f068ea099f233.tar.gz | |
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: 4d603ccf0713ade69d98e452b991a4d1d71c144a)
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
(cherry picked from commit e3dbded499f0bd1e71abb0650ae98fd9ade94250)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/parse/parse_py')
0 files changed, 0 insertions, 0 deletions