haskell / haskell/cabal

`<pkg-name>.cabal.up` for the glob wary

Open
#8,075 1 comment 0 reactions 0 assignees View on GitHub
Cabal: file format re: globbing type: discussion
Dominant language
Haskell
Stars
1.7k
Forks
750
Avg merge
4d 3h
Merged PRs (30d)
28

Description

I'm wary of using any glob-like features in the `.cabal` file (and project file). I want reproducible builds and being explicit helps get us there. I don't want to depend on whatever state my file system is in. Globs don't tell me I'm including junk files or am missing essential files that were not checked in to source control.

Could we take all the globbing features and put them in upstream file from which we then generate a `.cabal` file with globs expanded?

`.cabal.up` -> `.cabal`

> EDIT: note the fact that hpack "works" is because there is clear stage separation. package.yaml is compiled to pkgname.cabal, and pkgname.cabal is used as input to actual build tooling. Blurring the boundary, requiring to .cabal files to be interpreted before further consumption it tricky.
https://github.com/haskell/cabal/issues/5343#issuecomment-521590517

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.