Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Better handling of case where local package is named the same as a snapshot package but does not define a library component #2195
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: fpco/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