Closed
Description
The resolution for #1145 / #1027 is to replace some long paths with 8 character SHAs on windows, due to the MAX_PATH limitation. It would be good to store a file, maybe called SHA/stack-path
, with the path that would have been used in place of the SHA. This is useful for a variety circumstances:
- If a user is curious what's in the directory.
- If garbage collection gets implemented at some point. (stack rm command #133)
- It will allow SHAs to also be used for snapshot dependencies. The contents of the snapshots folder is scanned and parsed as part of
stack init
- https://github.com/fpco/stack/blob/master/src/Stack/Init.hs#L229
It gets a little bit tricky to ensure that every possible execution involving these paths will also create the path
file, though. These paths are used in quite a few places, and often they get created be external tools.
/me shakes fist menacingly at MAX_PATH