cabal
cabal copied to clipboard
Official upstream development repository for Cabal and cabal-install
The question [comes from Reddit](https://www.reddit.com/r/haskell/comments/wm656h/just_released_cabal_3810/ik97kj4). Perhaps it may bring some benefit? Even if only in terms of popularizing text-2.0...
Current binary releases of `cabal-install` are not statically linked, thus depending on `glibc`, which makes them unusable on `musl`-based distros like Alpine Linux. It'd be nice if statically-linked binary releases...
I have a script that invokes cabal with `--with-ghc=...`, `--with-ghc-pkg=...`, `--with-gcc=...`, etc. for cross-compiling to Android. It works great for most packages, but fails for a package with Build-type: Custom,...
This is expanded version [of this comment](https://github.com/haskell/cabal/issues/3072#issuecomment-174487089): Currently, the grammar for the `default` field is limited to ``` default: ``` This is perfectly sufficient for properly used automatic flags (i.e....
fix #5974 #7727 This is a cheap fix via straightforward extension of #6102 --- Please include the following checklist in your PR: * [ ] Patches conform to the [coding...
- Closes #8090. **TODO** - [ ] Check compatibility with #6248. --- Please include the following checklist in your PR: * [x] Patches conform to the [coding conventions](https://github.com/haskell/cabal/blob/master/CONTRIBUTING.md#conventions). * [...
It is quite common to alternate normal and profiling builds while developing. Currently, cabal uses the same build directory for both, which results in a lot of rebuilding. The current...
Switch between profiling and non-profiling builds is a fairly common usecase so supporting this without forcing a recompile is pretty useful. Please include the following checklist in your PR: *...
See https://github.com/haskell/hackage-security/runs/7814984300?check_suite_focus=true ``` tests/TestSuite/InMemRepo.hs:17:1: error: Ambiguous module name ‘Distribution.Text’: it was found in multiple packages: Cabal-3.6.0.0 Cabal-syntax-3.8.1.0 ``` Edit: this was first spotted in cabal CI, but the link I...
As in the title. `cabal new-configure --disable-optimization` doesn't actually disable optimization if `ghc-options` in the cabal file have e.g. `-O2`. This works with the old `cabal configure`.