Should BB_DEFAULT_UMASK be set with ?=
Quoted 6 lines · Rasmus Villemoes via lists.openembedded.org
Hi,
Suppose I want to define
BB_DEFAULT_UMASKin site.conf or local.conf (I do have a use case for setting it to 002). But bitbake.conf includes those files before it then goes on to use an unconditional assignment
Quoted 6 lines
BB_DEFAULT_UMASK= "022"So how/where is one supposed to be able to set
BB_DEFAULT_UMASK? Should the assignment in bitbake.conf be ?= or perhaps ??= instead? Or should the assigment instead be moved above the inclusion of the user's configuration files?
ping (and cc += RP)
Quoted 7 lines · Rasmus Villemoes
Quoted 6 lines · Rasmus Villemoes via lists.openembedded.org
Hi,
Suppose I want to define
BB_DEFAULT_UMASKin site.conf or local.conf (I do have a use case for setting it to 002). But bitbake.conf includes those files before it then goes on to use an unconditional assignment
Quoted 8 lines
Quoted 6 lines
BB_DEFAULT_UMASK= "022"So how/where is one supposed to be able to set
BB_DEFAULT_UMASK? Should the assignment in bitbake.conf be ?= or perhaps ??= instead? Or should the assigment instead be moved above the inclusion of the user's configuration files?ping (and cc += RP)
We have a general problem that not all defaults can be altered from all contexts. We can come up with some set of rules that values in file X after certain includes should be ??= and before, they should be ?= and in recipes should be = and so on but that then presents two problems, that there are still cases where users can't set as they need/want and the migration problem where changing to that model would break users.
So in short, send a patch and we can change it. It was assumed people wouldn't need/want to change the default umask as that does have quite far reaching implications.
Cheers,
Richard