Artem Pelenitsyn
Artem Pelenitsyn
I have the same problem as shown above (404 from fpco).
FTR, Stack hit it and worked around by changing the source code to use package imports (which eliminates ambiguity): https://github.com/commercialhaskell/stack/pull/5886
I don’t want to argue one way or another, but I feel like some people will get upset about this change: after all, PVP doesn’t have universal support (in this...
As I said, I'm not against merging it, so, by all means… Squash is the next level: presently, even the first commit message (which I usually expect to have some...
@mergify rebase
> After taking a closer look at this, I went with adding a new page. This way I could compare and contrast, be consistent and avoid duplication. Having source repos...
Maybe I went ahead of myself here: the current version of that page still looks more like a reference + some commentary rather than a full-fledged guide. I think it'd...
@Mikolaj I am on the verge. My first concern is this change: ``` cabal-package-description-file cabal-project-description-file + source-repositories cabal-config-and-commands external-commands setup-commands ``` I'm not sure it makes sense to have such...
Absolutely. #424 looks related.