From 2895bcf95a1ecb7feea1c6b458d8431cbf2c64f0 Mon Sep 17 00:00:00 2001 From: Phil Blundell Date: Wed, 24 Apr 2013 13:07:47 +0100 Subject: sstate: Set umask to 002 before packaging runs Otherwise we might end up creating directories under sstate-cache with whatever random umask has been selected for the task that we're trying to package. This would be a bad thing since it might result in losing group write access for newly created dirs, and/or losing group read access for the sstate files themselves. (From OE-Core rev: d8c4f442c41bf3ac5e064630657cd3fa1b5c43b1) Signed-off-by: Phil Blundell Signed-off-by: Saul Wold Signed-off-by: Richard Purdie --- meta/classes/sstate.bbclass | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'meta/classes/sstate.bbclass') diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass index 67ddc466ce..79d38304fd 100644 --- a/meta/classes/sstate.bbclass +++ b/meta/classes/sstate.bbclass @@ -532,7 +532,11 @@ python sstate_task_postfunc () { sstate_install(shared_state, d) for intercept in shared_state['interceptfuncs']: bb.build.exec_func(intercept, d) + omask = os.umask(002) + if omask != 002: + bb.note("Using umask 002 (not %0o) for sstate packaging" % omask) sstate_package(shared_state, d) + os.umask(omask) } -- cgit v1.2.3-54-g00ecf