-
Notifications
You must be signed in to change notification settings - Fork 842
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
solver not considering cabal flags #1071
Comments
Correct, that's the current behavior, since part of the solver step is to determine flags for us. It could be argued that explicit flag settings present in stack.yaml should be respected. It shouldn't be hard to implement this, want to take a crack at such a change and report how it works on your project? |
I've tried an implementation (see referenced merge request). @eallik, would you mind testing how it works for your project? |
Consider user-specified package flags in stack solver #1071
Implemented by #1143. |
* master: (59 commits) Ignore global database when copying precompiled packages #1146 Revert an unneeded change to 'runAndLog' Remove old GHCJS unpack directory if it exists Allow "stack setup ghcjs-0.1.0.20150924_ghc-7.10.2" Properly unzip GHCJS on windows (stack setup) Consider user-specified package flags in stack solver #1071 Fix a warning Colored build status in filewatch mode Add NixOS to 'How to install'. Include NixOS information #1118 Style improvements for Docker compatibility check Fix `awaiting pr` label link Fix GHC 7.8 build Docker: check host's stack compatibility by attempting to run in container and caching the result (#974) Fix formatting in `explicit-setup-deps` section Provide more information about changed files Compile custom Setup.hs instead of interpreting them (fixes #1041) Detect when hpc report gives trivial 100% #1009 Unified coverage report #579 Recommend extra-dep in yaml_configuration.yml ...
when I add this
to the
flags
section ofstack.yaml
,stack build
starts complaining about missing dependencies (random
andexecutable-path
) and proposes addingrandom-1.1
andexecutable-path-0.0.3
toextra-deps
, however, the next run ofstack build
complains aboutrandom-1.1
and suggests something closer to1.0.*
is needed. So I remove the 2 newly added items fromextra-deps
and try to makestack solver
figure it out on its own. However,stack solver
surprisingly responds with "no changes needed".— does this mean
stack solver
doesn't take into account theflags
section instack.yaml
?The text was updated successfully, but these errors were encountered: