cargo-cabal VS Cabal

just saw this : https://github.com/yvan-sraka/cabal-pack

Cabal has a lot of dark corners once you stray from the happy path. Just checked and I'm currently subscribed to 37 threads on the issue tracker, and I'm not a maintainer. A lot of these are related to lesser-used features like cabal scripts, environment files and doctests (though I think all of these things would used more if they were more reliable), but there's also plenty of stupid stuff like: - https://github.com/haskell/cabal/issues/3313 - https://github.com/haskell/cabal/issues/8527 - https://github.com/haskell/cabal/issues/8391 - https://github.com/haskell/cabal/issues/7789 - https://github.com/haskell/cabal/issues/6888 - https://github.com/haskell/cabal/issues/6999 - https://github.com/haskell/cabal/issues/5271

By the way, there are some open issues for the command to add a package in Cabal.

That's interesting. Could you could open a an issue about this? https://github.com/haskell/cabal/issues

At the moment, cabal-install doesn't support hpack natively but if the project can be build with cabal-install, you can run hpack manually to produce the .cabal file and utilise dr-cabal after that :)

Hm thanks for that, could try out some of those ideas. Here's the github issue i opened for this: https://github.com/haskell/cabal/issues/8580

Would really love it if the Cabal documentation had this as its own, highly visible entry. I submitted a pull request to that end.

Sometimes cabal's output is confusing with regards to optimization levels: https://github.com/haskell/cabal/issues/6221

Direct link to changelog: https://github.com/haskell/cabal/blob/master/release-notes/cabal-install-3.8.1.0.md

For example, this linked issue describes what appears to be a change, but is how I thought cabal already worked, so now I'm confused.