Repository navigation
Better handling of case where local package is named the same as a snapshot package but does not define a library component #2195
Description
There is a bit of a funky corner case where you can have a package named the same as some snapshot package, but if it doesn't define a library it doesn't shadow the snapshot.
For example, with this commit on stackage-server: commercialhaskell/stackage-server@5142f09
If you already have hoogle-4 built, then it will actually just use that one. Since the git repo of hoogle 5 doesn't provide a library component, it doesn't end up shadowing the snapshot hoogle-4.
If you don't have hoogle-4 built, you'll get
setup-Simple-Cabal-1.22.7.0-ghc-7.10.3: At least the following dependencies
are missing:
hoogle -any
Activity
[-]Handle case where local package is named the same as a snapshot package but does not define a library component[/-][+]Better handling of case where local package is named the same as a snapshot package but does not define a library component[/+]Check for deps on exe-only packages #2195
Check for deps on exe-only packages #2195
Check for deps on exe-only packages #2195
Merge pull request #3505 from commercialhaskell/2195-dep-on-exe
snoyberg commentedon Oct 24, 2017
Implemented via #3505
Check for deps on exe-only packages commercialhaskell#2195