[Hackage] #454: file permissions of installed files on windows
Hackage
trac at galois.com
Mon Jan 26 09:57:20 EST 2009
#454: file permissions of installed files on windows
----------------------------+-----------------------------------------------
Reporter: Toxaris | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Cabal-1.6
Component: Cabal library | Version: 1.6.0.1
Severity: normal | Resolution:
Keywords: | Difficulty: normal
Ghcversion: 6.10.1 | Platform: Windows
----------------------------+-----------------------------------------------
Comment (by duncan):
For unix I think it's clear we should do the same as `install -m644` for
data files and whatever the normal thing is for executables. That's what
everone else does.
For Windows, I've no idea. The notion of permissions is so completely
different. I'm not even sure that copying permissions makes any sense
since it goes via a C `struct stat` which cannot represent Windows ACLs.
Can we get away with not setting any permissions at all and just inherit
all defaults? The only time we currently set permissions is when creating
the temporary file when we open with mode `0o600`. On Windows this appears
to do precisely nothing. It is no different to creating a file with
default permissions.
So here's the concrete proposal:
* Unix: set explicit permissions upon install for executable and non-
executable files as appropriate.
* Windows: never set or copy any permissions ever, inherit all defaults.
--
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/454#comment:6>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects
More information about the cabal-devel
mailing list