By: Tom Sydney Kerckhove <syd@cs-syd.eu>
Keep cabal's ghc environment file out of the tree The previous commit swept it in: finding the dead extensions needed a standalone ghc that could see the project's packages, and `cabal build --write-ghc-environment-files=always` leaves one at the root. It holds absolute paths into one machine's cabal store, so it belongs to nobody but the machine that wrote it.
Total
8s
Created Started Finished
| Time to Start | Worker time | Duration | Time to finish | Idle | |
|---|---|---|---|---|---|
| Config | 0s | 0s | 0s | 0s | 0s |
| Eval | 0s | 7s | 7s | 8s | 0s |
| Build | 7s | 0s | 0s | 7s | 0s |
| Suite | 0s | 8s | 8s | 8s | 0s |