Relink-only seems to mess up dependency tracking
Open
blocked: upstream
cabal-install: v2-build system
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
If we have a project with multiple libraries, with Y depending on X, if I make a change to X, and then call new-build in Y, it will not notice it needs to relink it with X. However, once I get in this situation, it seems something breaks and it will not notice it needs to recompile even when this involves more than relinking.
Contributor guide
Assessment
This issue has not been assessed yet.