|Summary:||app-portage/layman should feature a umask setting in layman.cfg|
|Product:||Gentoo Linux||Reporter:||Wolfram Schlich (RETIRED) <wschlich>|
|Component:||Current packages||Assignee:||Gunnar Wrobel (RETIRED) <wrobel>|
|Package list:||Runtime testing required:||---|
Description Wolfram Schlich (RETIRED) 2007-07-27 16:34:29 UTC
All root accounts on machines I administer have a umask of 0077 set via /root/.bashrc. That leads to problems with layman, as all newly created files of repositories checked-out by layman are not readable by the portage user. I have written a wrapper script I am using from cron to run "layman -S" on a daily basis that sets a safe umask of 0022 before running layman. So far, so good. Unfortunately sometimes I need to run "layman -S" by hand and I *always* (yes) forget to use my wrapper script instead or to set a proper umask by hand prior to running layman, so I run into this permission problem. The IMHO best solution would be a simple feature allowing to set the umask in layman.cfg, with 0022 as the safe default.
Comment 1 Wolfram Schlich (RETIRED) 2008-04-02 12:01:39 UTC
Comment 2 Robert Buchholz (RETIRED) 2008-06-01 19:58:43 UTC
I would even go further and say that it should always work with umask 0022. All other settings just break normal usage.
Comment 3 Gunnar Wrobel (RETIRED) 2008-06-02 16:15:28 UTC
Finally in CVS (layman-1.2.0). Sorry for the delay.