-
Notifications
You must be signed in to change notification settings - Fork 843
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
Cabal 2's internal libraries don't work with HEAD #3361
Comments
Not certain, but: it seems like a simple workaround for this may be that, during the cabal file parsing step, to simply remove any build-depends referring to an internal library. I'm not sure if Cabal will then handle the build correctly from that point, but it's worth a shot. |
This should resolve both #3364 and #3361. There is a test case included that should address both of them as well. This is still relatively hacky. We will eventually be overhauling the component system more dramatically to support Backpack with #2540 (CC @ezyang). This may still have some problems due to the upstream issue haskell/cabal#4763, but at least in theory we're matching the behavior of upstream. We can consider workarounds after that issue comes to a conclusion.
This should be resolved by #3430. It would be great if you could test that branch before this gets merged to master. |
Closing this one off - please re-open if #3430 doesn't solve it. |
Cabal 2 support has just landed in HEAD with #3288 (hurrah), but one of the shiny new features doesn't work with stack yet: internal libraries (introduced in haskell/cabal#3022). A short demonstration:
I think that this ought to work as-is (that is, without anything internal-library-specific in stack.yaml), but it wouldn't be a disaster if it needed some magical incantation.
The text was updated successfully, but these errors were encountered: