-
Notifications
You must be signed in to change notification settings - Fork 848
drop-packages: Cabal
is silently ignored
#5707
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
I think that |
With my investigation above and the updating of the documentation, I am going to close this issue. |
Thanks for the explanation, @mpilgrem ! |
As described in the resolution to #5707, Cabal is no longer included in LTSs so this has no effect. It would be nice to list *which* LTS dropped it -- see FIXME.
As described in the resolution to #5707, Cabal is no longer included in LTSs so this has no effect. It would be nice to list *which* LTS dropped it -- see FIXME.
As described in the resolution to #5707, Cabal is no longer included in snapshots, so dropping it has no effect.
As described in the resolution to #5707, Cabal is no longer directly included in snapshots, so dropping it has no effect. P.S. I accidentally discovered another poorly-rendered Note, so I fixed it at the same time.
Entry
in
stack.yaml
seems to be silently ignored.So working around
extra-deps: Cabal
is ignored when.cabal
file does not haveCabal
dependency #5706according to the recipe in
extra-dep
is ignored when other version already in snapshot #5679fails.
The text was updated successfully, but these errors were encountered: