On 08/09/2011 07:26 AM, Paul Sokolovsky wrote:
Hello Alexander,
On Mon, 8 Aug 2011 12:39:41 +0200 Alexander Sack asac@linaro.org wrote:
ok spads from IS gave better suggestion than using umask in .bashrc. Now, we propose that you set alias for git like:
alias git='UMASK=002 git'
I understand the logic here - set umask only for git, but would that really work? I kinda get used that aliases are interactive session thing, and man reads:
Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt (see the description of shopt under SHELL BUILTIN COMMANDS below).I'm not sure how exactly git over ssh works though.
And whatever way of umask setting should be, did IS consider implementing it via global /etc/profile or via profile templates clones by adduser or similar tool, to alleviate that burden for the users?
There's another way to do this which doesn't require updating UMASK's or aliases. You can use setfacl as described here: https://wincent.com/wiki/Git_repository_access_control
I've used this on multiple projects.