-
Notifications
You must be signed in to change notification settings - Fork 701
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
Bump Cabal library and cabal-install version to 3.7 #7569
Comments
@emilypi: am I right we can do that fine already? |
@Mikolaj yeah we're good. |
Not sure why, but
One half of the job seems to be missing still, or am I misunderstanding something? |
I think this issue is about Cabal the library and no cabal-install, note the |
There's a value in
This is to do away with the paths module whose sole purpose was to do this, and it screwed up our ability to produce coverage. Right now, I think it deserves its own dedicated module. Just haven't had time. |
Ah, I wasn't aware that "Cabal" (capital) refers to strictly the library only. I was going to report a new issue but then found this one and it matched in my mind.
Thanks for the pointer, I give it a try. |
Move `cabalInstallVersion` to its own module `Distribution.Client.Version` as suggested by @emilypi at haskell#7569 (comment).
Thanks @andreasabel - I think as long as this sits in its own dedicated namespace so it doesn't get lost and we make sure it's on the release checklists, this should be sufficient. |
PR at #7683. |
Move `cabalInstallVersion` to its own module `Distribution.Client.Version` as suggested by @emilypi at haskell#7569 (comment).
Fix #7569 for cabal-install: bump to 3.7
Development version should not be equal to release version.
This is blocking development on #7489, as the flag
--enable-build-info
is guarded s.t. that it can not be accidentally used with older Cabal versions.The text was updated successfully, but these errors were encountered: