-
Notifications
You must be signed in to change notification settings - Fork 16
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
haxr does not build with ghc-9.0 due to HaXml #30
Comments
Hmm, good question. Let's see if @phadej replies to that ticket, I'm not sure I understand the objection. |
Out of curiosity, what exactly did you have to change to get it to build with GHC-9.0? I don't seem to see any relevant changes in that PR you linked. |
Ah, the changes are in the preceding commits (not mine), but there was no Hackage upload... 🤦 |
I believe it is this change that requires a new release rather than a revision alas. |
Just for future reference, I found the relevant discussion here: hackage-trustees/malcolm-wallace-universe#9 . Maybe it would be easiest just to set up your own fork. I'd be happy to help maintain it as well if you give me access. |
Yes, nod, but how to do the import is my main stumbling block? |
Okay Malcolm added me as a Hackage maintainer of HaXml this week: so I should be able to upload a new version soon. |
Re: what kind of org to make, if your intention is to just support HaXml, then better keep it to that for now! I will definitely join you there, ping me or post a link here! |
Sure thing, thanks |
I have released HaXml-1.25.6 on Hackage Hopefully it can go into Stackage Nightly soon |
Well maybe I closed prematurely, but I see you already enabled 9.0, thanks. |
The latest release of |
Yay, thanks! |
Unfortunately HaXml does not build yet with ghc-9.0: hackage-trustees/malcolm-wallace-universe#11.
I actually only need it for haxr... I was told to make my own fork if I want to upload a fixed HaXml...
Just wondering what is the best approach here in terms of maintenance. Any thoughts or suggestions?
The text was updated successfully, but these errors were encountered: