-
Notifications
You must be signed in to change notification settings - Fork 71
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
Bring everything up to date #52
Conversation
Both packages had new releases. This commit modifies Euterpea.cabal so that it accepts those versions and Euterpea can be compiled with the most recent versions of bytestring and HCodecs.
Incidentally, the homepage instructions are also out-of-date in a lot of ways:
|
As a Hackage trustee, I made a revision with version bumps: The revision is not sufficient for Cabal (because revisions cannot change resolver: nightly-2022-06-17
extra-deps:
- Euterpea-2.0.7@sha256:a885d2f3e82680284a85822d1f1b0e39ae44afbd50e61bf92e38ddbc7694b3b9,2683
- PortMidi-0.2.0.0@sha256:0671e36ec72e95138bf396234b205864a8a6d0ee353e09e01cbfd57004c56f40,2383 |
I have deleted much of the conversation here. I generally do not moderate conversations on repos I maintain, but I draw the line at people taking digs at my life choices as it has nothing to do with the library. I suggest those who were involved in this PR fork the repo instead. |
|
As a Hackage trustee, I made another revision with version bumps: |
Can a new hackage package be created for a forked project? I'll be convenient to have a community version to keep compatibility. |
To match Euterpea's revision (-r2) at hackage mentioned by Bodigrim [here](Euterpea#52 (comment)).
This builds with GHC 9.2.3 and Cabal 3.6.2.0.
It incorporates all other currently-open PRs (#38, #47).
Initially inspired by this Reddit post, although I've been meaning to pick my own copy of HSoM back up for a while anyway, and I'd much rather make these small fixes than faff about installing an older toolchain.