Thanks everyone for the lively discussion last week. I think we all
understand better now about environment files.
GHC reading environment files by default doesn't seem to be a problem
as it is just like having more packages installed in the global
package DB. This could be convenient.
The
Almost every day now I receive an e-mail from GitLab titled "Remote
mirror update failed", which contains something like:
To
! [remote rejected] wip/dmd-arity -> wip/dmd-arity (cannot
lock ref 'refs/heads/wip/dmd-arity': is at
e1cc1254b81a7adadd8db77c7be625497264ab2b but expected
Hi *,
On Fri, 5 Apr 2019 at 12:09, Matthew Pickering
wrote:
>
> [...]
>
> Therefore, it seems the correct course of action is to stop cabal
> generating the environment files by default. If user's still want to
> use them then they are easy to enable globally via a configuration
> setting.
>
>
> Did you mean "What is the TcHsSyn counterpart to TcMType.zonkTcTyVar"?
D'oh. Yes, I did.
> But it's never a bad idea to document more.
I've documented all the wisdom from here in this wiki page [1]! Feel
free to edit it if there are any corrections to be made.
Ryan S.
-
[1]
