-
Notifications
You must be signed in to change notification settings - Fork 710
cabal check doesn't account for conditionals #4629
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
Comments
@bgamari a quick workaround (until this is fixed in lib:Cabal & deployed on hackage) is that you can make two releases which differ only by patch-level, and let the solver pick the right one for the respective compiler (there's at least another package who does this on Hackage, but for other reasons). So i.e. release
This has also the benefit that |
There is this comment in the code: https://github.com/haskell/cabal/blob/master/cabal-install/src/Distribution/Client/Check.hs#L62 Does somebody know how to patch that in Hackage, or is there a reason for it to be like that? I assume, this is a non-trivial issue, as you either should make |
Hackage check seems to be done here: https://github.com/haskell/hackage-server/blob/8cebbe6c6341537b1c75281482cc1ca9a5c4153a/Distribution/Server/Packages/Unpack.hs#L290
|
I am afraid that haskell-language-server hackage release is blocked on this (via ghc-api-compat). |
@jneira fyi, I am working on a patch that drops the |
In
binary-serialise-cbor
we are trying to provideexposed-modules
for GHC 7.8, wherereexported-modules
is not supported. For instance,Unfortunately,
cabal check
fails on this with,It seems that Cabal doesn't account for the conditional when computing this check.
The text was updated successfully, but these errors were encountered: