PMS is currently silent on umask settings. seems like a glaring oversight when ebuilds rely on this via `cp` and such command.
What do you suggest, and what does Portage do? umask 022 everywhere in the ebuild environment?
documenting `umask 022` as the execution environment seems like the only reasonable thing. portage has been doing this "forever" afaict. should also note that the umask is not preserved between phase functions and is always reset to the initial value.
Created attachment 803665 [details, diff] ebuild-format.tex: Document that umask is set to 022 Please review.
(In reply to Ulrich Müller from comment #3) lgtm, thanks
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/proj/pms.git/commit/?id=2c69291b26fea14b6a93f1bf6b4f0bfd7f74f7b9 commit 2c69291b26fea14b6a93f1bf6b4f0bfd7f74f7b9 Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2022-09-07 06:35:09 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2022-09-07 06:35:09 +0000 ebuild-format.tex: Document that umask is set to 022 Portage has been doing this since 2001. Closes: https://bugs.gentoo.org/868669 Reported-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Ulrich Müller <ulm@gentoo.org> ebuild-format.tex | 3 +++ 1 file changed, 3 insertions(+)
