Handle abi-depends correctly in ghc-pkg
When inferring the correct abi-depends, we now look at all the package databases in the stack, up to and including the current one, because these are the ones that the current package can legally depend on. While doing so, we will issue warnings: - In verbose mode, we warn about every package that declares abi-depends:, whether we actually end up overriding them with the inferred ones or not ("possibly broken abi-depends"). - Otherwise, we only warn about packages whose declared abi-depends does not match what we inferred ("definitely broken abi-depends"). Reviewers: bgamari Reviewed By: bgamari Subscribers: rwbarton, thomie, carter GHC Trac Issues: #14381 Differential Revision: https://phabricator.haskell.org/D4729
Showing
- testsuite/tests/cabal/cabal05/cabal05.stderr 4 additions, 0 deletionstestsuite/tests/cabal/cabal05/cabal05.stderr
- testsuite/tests/safeHaskell/check/pkg01/safePkg01.stdout 8 additions, 8 deletionstestsuite/tests/safeHaskell/check/pkg01/safePkg01.stdout
- utils/ghc-pkg/Main.hs 127 additions, 15 deletionsutils/ghc-pkg/Main.hs
Loading
Please register or sign in to comment