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

Don't check in stack.yaml #17

Closed
wants to merge 1 commit into from
Closed

Don't check in stack.yaml #17

wants to merge 1 commit into from

Conversation

Lysxia
Copy link
Collaborator

@Lysxia Lysxia commented Apr 25, 2020

Having stack.yaml not checked in makes it easier for different people to use different resolvers (personally, so I can use the same resolver in all Haskell projects). Instead, there is now a stack-default.yaml and that adds only one extra cp at the very beginning for most people.

I also upgraded the resolver to lts-14.27, but can add back a version with lts-12.26 if prompted.

@dunnl
Copy link
Member

dunnl commented Apr 27, 2020

I'm not sure removing stack.yaml is the right thing to do. This and this seem to lean in favor of leaving it in---granted these answers are from the same person and those questions aren't directly about this situation. I don't think overriding the resolver is common although I see why some people might want to.

Stack apparently has or had a --resolver=global option according to commercialhaskell/stack#645. I think it would be easier to either override like this, or else maintain a local stack.yaml and configure .gitignore to ignore the local version (and the modified .gitignore too I guess?). Is there a way to configure stack to always use a custom resolver?

@Lysxia
Copy link
Collaborator Author

Lysxia commented Apr 27, 2020

Fair enough. There doesn't seem to be an option in stack to change this but another solution I just realized is to alias stack to stack --stack-yaml mystack.yaml or set the environment variable STACK_YAML=mystack.yaml.

@Lysxia Lysxia closed this Apr 27, 2020
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.

2 participants