Skip to content

Lower library compatibility version to 1.25, since 1.25 is dev series… #3939

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

Merged
merged 1 commit into from
Oct 7, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions cabal-install/Distribution/Client/ProjectPlanning.hs
Original file line number Diff line number Diff line change
Expand Up @@ -1112,7 +1112,7 @@ elaborateInstallPlan verbosity platform compiler compilerprogdb pkgConfigDB
-- Only non-Custom or sufficiently recent Custom
-- scripts can be build per-component.
= (fromMaybe PD.Custom (PD.buildType pd) /= PD.Custom)
|| PD.specVersion pd >= mkVersion [2,0,0]
|| PD.specVersion pd >= mkVersion [1,25,0]
-}

elab0 = elaborateSolverToCommon mapDep spkg
Expand Down Expand Up @@ -2357,9 +2357,7 @@ defaultSetupDeps compiler platform pkg =
-- breaking changes to the Cabal API that Setup.hs scripts use.
-- So for old custom Setup scripts that do not specify explicit
-- constraints, we constrain them to use a compatible Cabal version.
-- The exact version where we'll make this API break has not yet been
-- decided, so for the meantime we guess at 2.x.
cabalCompatMaxVer = mkVersion [2]
cabalCompatMaxVer = mkVersion [1,25]
-- In principle we can talk to any old Cabal version, and we need to
-- be able to do that for custom Setup scripts that require older
-- Cabal lib versions. However in practice we have currently have
Expand Down