Don't use braces in fgl.cabal to allow building with MicroHs#116
Conversation
|
I did not even know that cabal supported braces. I'm more of a custodian than a real maintainer, but I see no reason not to do this. Is it possible to remove braces via a Hackage revision? It seems a little awkward to do an entire release just for this. |
It should be possible, however I'm not sure if MicroCabal actually considers revisions. cc @augustss |
|
MicroCabal ignores version numbers. It uses a consistent set of packages as defined by Stackage. |
But which .cabal file does it use? The one that was originally uploaded or the revised version? |
|
It uses the version number obtained from stackage to form the URL for download from Hackage. I think we can tweak the MicroCabal parser to accept braces. |
If I understand correctly, that means that it doesn't use the revised .cabal file, so a revision wouldn't fi the problem. |
|
I think Stackage includes revisions. |
|
I don't know why CI will not run, but this change is obviously harmless. |
Even Cabal proper would rather not to deal with brace syntax, so cleaning them up is a good thing anyway. |
MicroCabal unfortunately still uses the old .cabal file, however installing via git now works. Thanks! |
MicroHs: https://github.com/augustss/MicroHs
I can add a MicroHs action to the CI if you want, but it might either become outdated (if we pin the MicroHs version) or fail sometimes (when using the latest version). In any case, I also plan to build
fglin the MicroHs CI.