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

Last part of addressing #415 #5180

Merged
merged 3 commits into from
Mar 3, 2018
Merged

Last part of addressing #415 #5180

merged 3 commits into from
Mar 3, 2018

Conversation

hvr
Copy link
Member

@hvr hvr commented Mar 3, 2018

See commit comments; this completes the work for addressing #415
(NB: This PR only touches cabal-install)

hvr added 2 commits March 3, 2018 10:31
GHC 8.4.1-rc1 (GHC 8.4.0.20180224) unfortunately still shipped with a
devel snapshot of Cabal-2.1.0.0; but GHC 8.4.1 final will ship w/
lib:Cabal-2.2.0.0
As we can't predict the future, we also place a global upper
bound on the lib:Cabal version we know how to interact with:

The upper bound is computed by incrementing the current major
version twice in order to allow for the current version, as
well as the next adjacent major version (one of which will not
be released, as only "even major" versions of Cabal are
released to Hackage or bundled with proper GHC releases).

For instance, if the current version of cabal-install is an odd
development version, e.g.  Cabal-2.1.0.0, then we impose an
upper bound `setup.Cabal < 2.3`; if `cabal-install` is on a
stable/release even version, e.g. Cabal-2.2.1.0, the upper
bound is `setup.Cabal < 2.4`. This gives us enough flexibility
when dealing with development snapshots of Cabal and cabal-install.

This addresses haskell#415
@hvr hvr added this to the 2.2 milestone Mar 3, 2018
@23Skidoo
Copy link
Member

23Skidoo commented Mar 3, 2018

LGTM.

@hvr hvr merged commit 7ce486e into haskell:2.2 Mar 3, 2018
@hvr hvr deleted the pr/2.2/issue-415c branch March 3, 2018 21:59
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

Successfully merging this pull request may close these issues.

2 participants