Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better handling of case where local package is named the same as a snapshot package but does not define a library component #2195

Closed
mgsloan opened this issue May 26, 2016 · 1 comment

Comments

@mgsloan
Copy link
Contributor

@mgsloan mgsloan commented May 26, 2016

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

setup-Simple-Cabal-1.22.7.0-ghc-7.10.3: At least the following dependencies
are missing:
hoogle -any
@mgsloan mgsloan changed the title 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 May 26, 2016
@mgsloan mgsloan added this to the P2: Should milestone May 26, 2016
snoyberg added a commit that referenced this issue Oct 22, 2017
snoyberg added a commit that referenced this issue Oct 22, 2017
snoyberg added a commit that referenced this issue Oct 22, 2017
snoyberg added a commit that referenced this issue Oct 24, 2017
Check for deps on exe-only packages #2195
@snoyberg
Copy link
Contributor

@snoyberg snoyberg commented Oct 24, 2017

Implemented via #3505

@snoyberg snoyberg closed this Oct 24, 2017
tswelsh added a commit to tswelsh/stack that referenced this issue Nov 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants