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

Things that might be required for Cabal-2.0 (but things might have changed) #624

Open
wants to merge 1 commit into
base: ghc-8.0
Choose a base branch
from

Conversation

ddssff
Copy link
Contributor

@ddssff ddssff commented Feb 6, 2018

  • Ifdef changes in src-bin/Boot.hs to allow build with
    cabal-install-1.24 or cabal-install-2. If Cabal-2 is available
    this will prevent builds with cabal-install-1.24, but without
    this patch such builds are always impossible because the
    --allow-boot-library-installs flag is an error.
  • Remove upper bound 1.25 on Cabal build dependency. Cabal-install-2 has
    a build dependency on Cabal>=2, so there is no reason to support
    cabal-install-2 without allowing builds with Cabal-2.

  cabal-install-1.24 or cabal-install-2.  If Cabal-2 is available
  this will prevent builds with cabal-install-1.24, but without
  this patch such builds are always impossible because the
  --allow-boot-library-installs flag is an error.
* Remove upper bound 1.25 on Cabal build dependency.  Cabal-install-2 has
  a build dependency on Cabal>=2, so there is no reason to support
  cabal-install-2 without allowing builds with Cabal-2.
@ddssff
Copy link
Contributor Author

ddssff commented Feb 6, 2018

Removing that upper bound is probably wrong.

@ddssff ddssff changed the title I've just spent some time straightening out my 8.0 build, this is what I learned Things that might be required for Cabal-2.0 (but things might have changed) Apr 11, 2018
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.

None yet

1 participant