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

Update cabal-doctest.cabal #26

Closed
wants to merge 1 commit into from
Closed

Update cabal-doctest.cabal #26

wants to merge 1 commit into from

Conversation

amcphail
Copy link

@amcphail amcphail commented Nov 8, 2017

Bump upper Cabal dependency version

Bump upper Cabal dependency version
Copy link
Collaborator

@phadej phadej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm sorry, but I have to reject htis.
Cabal-2.1 isn't out yet. Use allow-newer.

Also <= is fishy. We'll have <2.3, when time is right.

I won't make any speculative releases. See https://github.com/hvr/head.hackage if we'll actually need to do some changes for testing GHC HEAD.

@RyanGlScott
Copy link
Collaborator

As it turns out, GHC HEAD now depends on a newer version of Cabal which doesn't currently build with the latest cabal-doctest on Hackage (1.0.3). In the meantime, I've submitted a patch at head.hackage.

@RyanGlScott
Copy link
Collaborator

..never mind. As explained here, Cabal-2.1 does indeed build with cabal-doctest-1.0.4—for the time being, at least.

When Cabal-2.2 is finalized, we'll bump the upper version bound. It's better to be safe than sorry with Cabal, given its relatively volatile API.

@RyanGlScott
Copy link
Collaborator

Superseded by #36.

@RyanGlScott RyanGlScott closed this Mar 8, 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.

3 participants