On Wed, Jan 26, 2011 at 10:20:02AM +0000, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote: > Why?
because the umask only affects files being created, not copied, which results in an inconsistent installation. all files, except the dumped .o files are world readable. if the umask were relevant for installation then it should apply to all files being installed. when installing software, the permissions are usually set explicitly in the makefile and not by letting the installing users umask affect them. most software installations also do not produce new files during installation, so the umask normally has no effect at all. it is therefore an unexpected behaviour, when i have to take care of my umask to avoid files being created with wrong permissions. greetings, martin.
