non-owner-writable files generated in ghc build process?

[Isaac Dupree]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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?)

I know, I can use `rm -rf` in order to unquestioningly follow UNIX
permissions model...

Isaac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGNJmgHgcxvIWYTTURAs5IAKCw5ND5vKLimSkIaclz5onqnNHVyACeKCPq
bBtTcqD+/qoG3gnDcAtLHc0=
=PUgp
-----END PGP SIGNATURE-----