-
Notifications
You must be signed in to change notification settings - Fork 711
custom-setup solving problem, is Cabal
version shared across all Setup.hs
?
#4295
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
Comments
cc @grayjay |
I have no idea where from the |
new-build requires 1.20 or later because 1.18 setup does not support We should make "minimum |
The problem is that new-build adds all packages from cabal.project to the list of targets for the dependency solver, so they all are required to have consistent dependencies. In this example, the solver would ideally choose the installed One solution is to enable --independent-goals for new-build. Then some packages in a project can be setup dependencies for others and be allowed to have different versions for their dependencies. /cc @dcoutts |
@grayjay thanks for the explanation! |
Note that the |
--independent-goals could be useful for using local packages as setup or build-tool dependencies in new-build. See haskell#4295 for an example of a dependency problem that requires --independent-goals. The flag is off by default.
I think the issue with building cabal-doctest was resolved with the --independent-goals flag. I opened a separate issue for enabling the flag by default: #6460 |
Happens only with GHC 7.8.4 and older.
With the code in ulidtko/cabal-doctest@742c2d0
Only if I add a
cabal-doctests >=1.0.1
bound toexample.cabal
's setup-depends, I'll get a solver error https://travis-ci.org/phadej/cabal-doctest/jobs/198593113This is very unfortunate, as I don't see why there can't be valid plan (
Cabal
forComponentSetup
should interfere withghc
/doctest
etc part of the--enable-tests
plan)The text was updated successfully, but these errors were encountered: