Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add stack.yaml file #463

Merged
merged 2 commits into from
Dec 28, 2017
Merged

Add stack.yaml file #463

merged 2 commits into from
Dec 28, 2017

Conversation

m-renaud
Copy link
Contributor

Running stack init fails if you're using a resolver newer than lts-7.24 because ChasingBottoms has not been in Stackage LTS releases since then. Since Stack is a common workflow people use we should support the most recent Stackage LTS versions out of the box.

In the stack.yaml file we add ChasingBottoms-1.3.1.3 as an extra-dep and default the resolver to 9.20 because lts-10.0 uses GHC 8.2 which is not supported all of the tools yet; ghc-mod is lacking support, for example. Once all tooling supports lts-10.0 we'll change the default resolver.

This also updates CONTRIBUTING.md, removing the stack init step because it is no longer needed.

This resolves #458.

`stack setup` fails due to ChasingBottoms missing from Stackage

We default to lts-9.20 because lts-10.0 is currently not supported by many
development tools (such as intero) because ghc-mod does not yet support GHC
8.2 (DanielG/ghc-mod#900).

This was tested and works with resolvers lts-10.0 and lts-9.20.

Using older resolvers <=lts-7.24 causes a conflict with the package ranges
specified in containers.cabal.
The stack.yaml file is now provided when the containers repo is cloned.
@m-renaud m-renaud requested a review from treeowl December 27, 2017 18:13
Copy link
Contributor

@treeowl treeowl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know too much about Stack (or even Cabal, really), so I'm content to defer to your expertise. Just one question: will the presence of this stack.yaml affect whatever the Stackage people do to put containers up today?

@m-renaud
Copy link
Contributor Author

Confirmed this will have no impact on Stackage snapshot generation: https://groups.google.com/forum/m/#!topic/haskell-stack/peD4SU0-S5c

@treeowl
Copy link
Contributor

treeowl commented Dec 28, 2017 via email

@m-renaud m-renaud merged commit e631b6b into haskell:master Dec 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot use stack for lts > 7.24
2 participants