GHCi should not fail to honour ghci.conf or .ghci if group writable
Any number of Linux distros support the idea of user groups, whereby when a new user is created there is also simultaneously a group created with the same name; ie, instead of
-rw-r--r--. 1 andrew users 19 Sep 5 08:29 ghci.conf
as us old traditionalists would have it, you get
-rw-rw-r--. 1 andrew andrew 19 Sep 5 08:29 ghci.conf
because the umask in such cases is 0002 instead of 0022.
There is entirely nothing unusual or incorrect about this approach, and it is followed, for example, in the Fedora family of distros.
GHC, however, is being a bit silly in emitting the following:
$ ghci
GHCi, version 7.6.3: http://www.haskell.org/ghc/ :? for help
Loading package ghc-prim ... linking ... done.
Loading package integer-gmp ... linking ... done.
Loading package base ... linking ... done.
*** WARNING: /home/andrew/.ghc/ghci.conf is writable by someone else, IGNORING!
Prelude>
Foremost the fact that the file is group writable is not a problem and the user's choice, //particularly// in this case because it's group writable in the user's group! Regardless of that, GHCi should not be ignoring files with other than 0644 permissions; this isn't .ssh/
.
Can this check and attendant behaviour be removed?
AfC
Trac metadata
Trac field | Value |
---|---|
Version | 7.6.3 |
Type | Bug |
TypeOfFailure | OtherFailure |
Priority | normal |
Resolution | Unresolved |
Component | GHCi |
Test case | |
Differential revisions | |
BlockedBy | |
Related | |
Blocking | |
CC | |
Operating system | |
Architecture |