Andreas Abel
Andreas Abel
On current master: ``` $ cabal path foo Error: [Cabal-7061] 'man' doesn't take any extra arguments: foo ``` This is a cut-and-paste coding error in PR - #8879 https://github.com/haskell/cabal/blob/9e5e815315794d4e5b8e69b36379ac04d0839c53/cabal-install/src/Distribution/Client/Main.hs#L1392-L1397 Copied...
We currently have 3 ways to put extra files into the sdist tarball, but all of these have special semantics: 1. `data-files`: files used by the package at runtime 2....
Closes #305. Published as `v1`, `v1.2`, `v1.2.12`.
**This repo is DEPRECATED. Please don't open any new issues or PRs here.** Instead, checkout the new repositories: - https://github.com/haskell-actions/setup - https://github.com/haskell-actions/hlint-setup - https://github.com/haskell-actions/hlint-run
I noticed that if I create or amend a commit while I also have unstaged changes, these will end up against intention in the auto-generated `dist/` and `lib/` parts of...
Lifted from - https://github.com/haskell/actions/issues/202#issuecomment-1467594951 Implementing @Mistuke's suggestion to install `cabal` before `ghc` would amount to swapping the entries in the `opts` record, which implicitly determines the order of installation: https://github.com/haskell/actions/blob/86bd3eda129ecad970079574dd4001961be531f8/setup/src/opts.ts#L161-L187...
Currently, the README has several workflows that just use `runhaskell`, which is unrealistic in practice. - Reduce the number of `runhaskell` workflows (1 seems sufficient) - Add a realistic workflow...
This test: https://github.com/haskell/actions/blob/ed063006efd303ff80efebeec18bb9261c26347e/.github/workflows/workflow.yml#L45-L47 does `/home/runner/.ghcup/bin/cabal update` (under Setting up cabal) but it seems to not affect `cabal build`. Maybe there are two conflicting `cabal`s in the PATH with different `.cabal`...
Errors during installation e.g. via `ghcup` should be lifted to the user rather than swallowed, to enable debugging (e.g. to find out which prerequisites may be missing). E.g. when attempting...
``` $ cabal build --constraint='bytestring >=0.12' --allow-newer=bytestring ... internal/Data/Attoparsec/ByteString/FastSet.hs:97:18: warning: [-Wdeprecations] In the use of ‘memset’ (imported from Data.ByteString.Internal, but defined in bytestring-0.11.5.0:Data.ByteString.Internal.Type): Deprecated: "Use Foreign.Marshal.Utils.fillBytes instead" | 97 |...