Fix multi-repl when only building some internal library targets
When combining together --dependency and --promised-dependency flags, we were using `Map.union` in the wrong place. If you had a dependency and promised-dependency from the same package (ie when using an internal library) then the promised dependency wouldn't be taken into account. The fix is straightforward, don't use `Map.union`. First create a list of everything and then create a map using `fromListWith`. Fixes #10775 (cherry picked from commit c2cdfc01)
Showing
- Cabal/src/Distribution/Backpack/Configure.hs 4 additions, 2 deletionsCabal/src/Distribution/Backpack/Configure.hs
- cabal-testsuite/PackageTests/MultiRepl/InternalLibs/cabal.out 16 additions, 0 deletions...l-testsuite/PackageTests/MultiRepl/InternalLibs/cabal.out
- cabal-testsuite/PackageTests/MultiRepl/InternalLibs/cabal.project 1 addition, 0 deletions...stsuite/PackageTests/MultiRepl/InternalLibs/cabal.project
- cabal-testsuite/PackageTests/MultiRepl/InternalLibs/cabal.test.hs 7 additions, 0 deletions...stsuite/PackageTests/MultiRepl/InternalLibs/cabal.test.hs
- cabal-testsuite/PackageTests/MultiRepl/InternalLibs/components/x/X.hs 1 addition, 0 deletions...ite/PackageTests/MultiRepl/InternalLibs/components/x/X.hs
- cabal-testsuite/PackageTests/MultiRepl/InternalLibs/components/y/Y.hs 1 addition, 0 deletions...ite/PackageTests/MultiRepl/InternalLibs/components/y/Y.hs
- cabal-testsuite/PackageTests/MultiRepl/InternalLibs/components/z/Z.hs 1 addition, 0 deletions...ite/PackageTests/MultiRepl/InternalLibs/components/z/Z.hs
- cabal-testsuite/PackageTests/MultiRepl/InternalLibs/foo.cabal 33 additions, 0 deletions...l-testsuite/PackageTests/MultiRepl/InternalLibs/foo.cabal
- changelog.d/pr-10841.md 11 additions, 0 deletionschangelog.d/pr-10841.md
Loading
Please register or sign in to comment