Describe stack/cabal situation in contributing guidelines
Clarification and motivation
We have stack.yaml
, hpack
files, .cabal
files, cabal.project
. There is some redundancy, normally repos have only a subset of these files. So a potential contributor will be confused.
Acceptance criteria
CONTRIBUTING.md
file should that we use stack.yaml
and hpack
, but we also commit .cabal
files into repository due to a regression in stack
and commit other Cabal files to let people build the project w/o stack
. And then say that if one wants to update any of these files, they should do that in stack.yaml
or hpack
files and run scripts/generate-cabal-files.sh
.