On 3/16/07, Dan Nicholson <[EMAIL PROTECTED]> wrote: > On 3/16/07, Jonathan Oksman <[EMAIL PROTECTED]> wrote: > > > The same semantics caused a simular bug with umask. My user > > (jonathan, group jonathan) got the default umask of 002 because of his > > uid being equal to gid. After compiling gpm and su-ing, I installed > > gpm user and group read-writable as root:root. Why? Because umask > > settings are controlled through /etc/profile, and su ignores it. > > I'm not a huge fan of that default umask, but I suggest you set a sane > default umask for whatever user is doing the building. I actually > expect that umask gets set to 022 (the default) after you su. But some > packages aren't smart about how they create files for installation and > don't set the permissions.
I take that back. umask is persistent across su, it seems. I think the right thing to do is still to set the umask to the default for whatever user is building/installing packages. > I would bet that gpm's Makefile simply copies the created files to the > install location. Most autotooled packages use install and specify > -m<mode> for the installed files. This is still true, though. Most packages set the right permissions on their own and don't rely on umask. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
