29 Apr
2007
29 Apr
'07
10:33 a.m.
On Sun, Apr 29, 2007 at 09:12:00AM -0400, Isaac Dupree wrote:
When I was doing `rm -r` on a build tree it pointed out that driver/split/ghc-split.prl and driver/mangler/ghc-asm.prl were write-protected. Tacking this down, they're generated from .lprl with unlit... then (in mk/suffix.mk) they are `chmod 444`-ed. Is this a problem? Is the purpose to remind people that those are generated files, so don't change them? (hmm... if someone has a restrictive umask like 027, will this circumvent it? would `chmod -w` make more sense?)
umask only affects file creation, not chmod.
I know, I can use `rm -rf` in order to unquestioningly follow UNIX permissions model...
Stefan