cabal
cabal copied to clipboard
haskell
Official upstream development repository for Cabal and cabal-install
I'm just an amateur Haskell user (neither beginner nor expert), and wanted to try the new multi-repl support in cabal 3.12. Below is a description of my frustration and some...
cabal-install will now use a version suffixed cache file for the index state. If you are regularly changing between cabal-install versions, this will be less annoying as you won't have...
The v2 API of Cabal uses `cabal.project` files to specify configuration, but this file currently has to be supplied through the `--project-file` flag. This is painful as `new-config` doesn't persist...
# UPDATE We seem to be converging to this plan: - Libraries get a new field: `test-only: Bool`, by default False. - Libraries with `test-only: True` can only be imported...
it seems like it generates an index.html thats only the haddocks for your local code, and presumably transitive deps via haddocks. how would i generate a one true index file?...
**Describe the bug** This is a regression starting with 3.14. The bug is not present in 3.12. Compiling `ghc-lib-parser` as a dependency of a project fails with ``` compiler/GHC/Parser/PostProcess/Haddock.hs:72:1: error:...
Ref.: https://github.com/haskell/cabal/issues/4548 When building sublibraries with cabal today, you end up with build paths like: ``` $pkg/l/$comp/build/$comp/ ``` note the duplicate `$lib` in there. Tracking this down, leads us to...
It looks like uploading documentation got broken: ``` $ cabal-3.12.1.0 upload -d /Users/abel/bin/src/test-framework/dist-newstyle/test-framework-0.8.2.2-docs.tar.gz Uploading documentation /Users/abel/bin/src/test-framework/dist-newstyle/test-framework-0.8.2.2-docs.tar.gz... Documentation successfully uploaded for package candidate... $ cabal-3.14.2.0 upload -d /Users/abel/bin/src/test-framework/dist-newstyle/test-framework-0.8.2.2-docs.tar.gz Uploading documentation /Users/abel/bin/src/test-framework/dist-newstyle/test-framework-0.8.2.2-docs.tar.gz......
This PR modifies how source distribution are packaged by `cabal-install:exe:cabal`: Before, if the name of the Cabal file did not match the actual package name, then `cabal sdist` would include...
The PR fixes the issue (#10721) by adding a new `js-options` field to cabal file that are passed to `componentJsGhcOptions`. Please advise on the testing strategy, if any. Thank you...
