`cabal list-bin` too sensitive to configuration?
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
Is `cabal list-bin` too sensitive to configuration?
It requires me to pass the same flags as to `build`. In contrast, `cabal-plan list-bin` does not require this.
(Example project taken from https://github.com/asr/pdfname.)
```
/pdfname$ cabal build --allow-newer=pdfname:base
(succeeds)
/pdfname$ cabal-plan list-bin pdfname
(succeeds)
/pdfname$ cabal list-bin pdfname
(after a 2 sec wait, fails)
Error: cabal: Could not resolve dependencies...
/pdfname$ cabal list-bin pdfname --allow-newer=pdfname:base
(succeeds)
```
I wonder whether `list-bin` could be more robust wrt. missing flags. Some flags do matter to find the correct executable (like `-w`), but some won't (like `--allow-newer`).
Contributor guide
Assessment
This issue has not been assessed yet.