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

Stack templates can't declare extra-deps #2014

Closed
jsteiner opened this issue Apr 8, 2016 · 2 comments
Closed

Stack templates can't declare extra-deps #2014

jsteiner opened this issue Apr 8, 2016 · 2 comments

Comments

@jsteiner
Copy link

jsteiner commented Apr 8, 2016

We're trying to write a stack template that depends on packages that aren't in Stackage. Thus, we want to supply our own stack.yaml. Unfortunately, when using stack new with the template, it ignores our supplied stack.yaml and fails because the LTS doesn't have all the packages to match our requirements. I should note that we are using --force, so the stack.yaml is being written, but isn't being used for the initialize step.

Expected:

stack new uses the supplied stack.yaml, including extra-deps in the initialize step.

Actual:

stack new fails because the lts-5.11 does not have all the package to match our requirements.

Stack version

$ stack --version
Version 1.0.4 x86_64
@mgsloan mgsloan added this to the Support milestone Apr 9, 2016
@mgsloan
Copy link
Contributor

mgsloan commented Apr 9, 2016

stack new --solver should do the trick.

Also related to #1390

@snoyberg
Copy link
Contributor

In newer Stack versions, if a stack.yaml is declared in the template then it is used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants