cabal
cabal copied to clipboard
haskell
Official upstream development repository for Cabal and cabal-install
``` $ git clone https://github.com/hvr/-.git 無 ... $ cd 無 $ runghc Setup.hs configure Configuring 無-0... $ runghc Setup.hs sdist Distribution quality warnings: No 'category' field. No 'description' field. Warning:...
Suggested by @tomjaguarpaw in the HF slack. Joachim suggested that we might want to suppress this when active-repositories is the default. I think it wouldn't be too much line noise...
There are a number of places (excluding custom setups, certain licenses, etc) where explicitly disallowing certain values of certain fields from solver build plans could be useful, or, alternately, warning...
Both `new-configure` and `new-build` seem to silently swallow these options at the moment.
This came out of some discussion on IRC. I started writing an issue, but on reflection I think there's a relatively plausible design sitting there, so I wrote it down....
``` $ cabal get bytestring $ cd bytestring-0.10.8.2 $ cabal new-configure -w ghc-8.4.1 $ cabal new-haddock --haddock-for-hackage … Documentation created: /home/simon/src/bytestring/dist-newstyle/build/x86_64-linux/ghc-8.4.1/bytestring-0.10.9.0/doc/html/bytestring-0.10.9.0-docs/index.html, /home/simon/src/bytestring/dist-newstyle/build/x86_64-linux/ghc-8.4.1/bytestring-0.10.9.0/doc/html/bytestring-0.10.9.0-docs/bytestring.txt Documentation tarball created: /home/simon/src/bytestring/dist-newstyle/bytestring-0.10.9.0-docs.tar.gz ``` But neither the...
`-v0` should never output anything to stdout. cabal-install should be silent in this mode of operation. If you enable `documentation: true` in a cabal file then a lot of junk...
**Describe the bug** `plan.json` includes also internal libraries which aren't always built. **To Reproduce** ``` $ cabal v2-install --lib overloaded ``` In `~/.ghc/.../environments/default` I get ``` package-id overloaded-0.1.3-0f5ef0185b0463d9c537b950ec837dc1f2c91bda0aab9c3e85c6116c29835dbf package-id overloaded-0.1.3-cbb948b926e47cefb1f7cce1fac8681fbaa99202a33cb5a0225d7225620c3ed2...
If you compile a project with `new-build` and move/delete the executable, cabal doesn't actually check for the executables existence. So if none of the inputs have changed since the last...
Fetching a `source-repository-package` seems to make a full clone of the repo: ``` $ cabal --version cabal-install version 3.5.0.0 compiled using version 3.5.0.0 of the Cabal library $ cat cabal.project...
