gbaz
"There are no line number indicators above." -- doesn't the line-number get listed as 93? You're right having an autofmt fix would be better. Unfortunately cabal-fmt is an external heavyweight...
what oleg means I believe is that if the package were uploaded _today_ fresh, the check would prevent that syntax to begin with. so this problem only affects "legacy" cabal...
I believe this was due to our host (equinix metal) undergoing infrastucture maintenance: https://status.equinix.com/history
ok i think i see the confusion. what i mean is why do we need any acid-state for any of this? can't we just compute it on the fly? before...
> Is supporting packages and source-repository-package likely to be difficult? My suspicion is that this is a matter of some flag plumbing, and not a huge conceptual obstacle.
This is still marked as a draft. What work remains?
there's no urgency, this is a maintenance change. might as well let it take the time it needs.
We ran into the same issue, to the point of making the project effectively uncompilable on some users laptops, and the pragmas flags suggested by @remeike did the trick. This...
would suggest that we move the non-reinstallable library list responsibility to ghc, which cabal can query per-version. that way as ghc slims down the list, cabal can adapt automatically.
My understanding from talking to past cabal developers and maintainers is that this is something we absolutely should seek to fix. For libraries, cabal builds and leverages a proper packagedb....