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

bad resolver recommends "nightly-2015-01-01", which confused me #241

Closed
radix opened this issue Jun 9, 2015 · 5 comments
Closed

bad resolver recommends "nightly-2015-01-01", which confused me #241

radix opened this issue Jun 9, 2015 · 5 comments
Assignees
Milestone

Comments

@radix
Copy link
Contributor

radix commented Jun 9, 2015

If I put resolver: nightly in my stack.yaml file (which I just tried), I got this message

AesonException "Invalid resolver value: nightly. Possible valid values include lts-2.12, nightly-2015-01-01, and ghc-7.10."

This made me think that nightly-2015-01-01 was the only nightly I could use for some reason. Of course I read "include" as "are", which was my mistake, but an easy one to make.

Showing the entire list of possible values would be nice, but perhaps infeasible? It would presumably require an HTTP request to Stackage, and may also be overwhelming given that there are presumably hundreds of nightlies.

@bitemyapp
Copy link
Contributor

@radix that or demonstrate the date format, explaining nightly as a special case.

@drwebb
Copy link
Contributor

drwebb commented Jun 9, 2015

It would be nice to just have 'nightly' as an option, can we use
http://www.stackage.org/download/snapshots.json

@snoyberg
Copy link
Contributor

snoyberg commented Jun 9, 2015

I'm definitely open to improvements to the wording to be less confusing. In fact, if you have a better approach, feel free to just edit it!

@drwebb Taking that approach would remove the possibility of having reproducible builds, as suddenly a new Stackage Nightly would change what your code is built against.

@snoyberg
Copy link
Contributor

Thanks for the PR. Should we close this issue?

@snoyberg snoyberg added this to the First stable release (0.1.0.0?) milestone Jun 10, 2015
@radix
Copy link
Contributor Author

radix commented Jun 10, 2015

Yeah, I'll close it. I mentioned what I think is a nice longer-term solution in #211 (comment).

Thank you for the review/merge!

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

No branches or pull requests

4 participants