hpack
hpack copied to clipboard
sol
hpack: A modern format for Haskell packages
Cabal >= 3.0 allows set notation in the [`tested-with`](https://cabal.readthedocs.io/en/3.4/cabal-package.html#pkg-field-tested-with) field, such as ```cabal tested-with: GHC == { 8.6.3, 8.4.4, 8.2.2, 8.0.2, 7.10.3, 7.8.4, 7.6.3, 7.4.2 } ``` When we use...
Please get ready for sublibraries. Cabal is mostly there. This is good for distribution of closely related libraries within a single package. ```cabal -- wanted pkgA.cabal name: pkgA library build-depends:...
https://github.com/sol/hpack/pull/490 moves `import` lines to the top of the stanza, but it only happens the first time `hpack` is called. Repro: 1. Run `rm *.cabal` 2. Add `verbatim: { import:...
``` ghc-options: - -XViewPatterns ``` > Warning: Instead of 'ghc-options: -XViewPatterns' use 'extensions: ViewPatterns' However, adding `extensions` field to `package.yaml` generates another warning: > WARNING: Ignoring unknown field "extensions" in...
Running into a bit of an issue, newer `stack` refuses to compile asm sources listed in `c-sources` and hpack doesn't have [`asm-sources`](https://cabal.readthedocs.io/en/3.10/cabal-package.html#pkg-field-asm-sources). Suggestions?
I saw this https://github.com/sol/hpack/issues/513 I'm opening a new issue about the same thing. YAML includes are inadequate for DRYing up even moderately-complex cabal config. Mostly due to the lack of...
- This has the potential to break packages for `cabal v1-`, and Hackage still uses `cabal v1-`: https://github.com/haskell/hackage-server/issues/821 - At first glance you might think that cabal files that use...
This is not a 100% baked idea, but hpack could accept defaults on the command line (and that could then be fed in by higher-level tools). Imagine if you have...
