Skip to content

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

Closed
andreasabel opened this issue Apr 11, 2022 · 3 comments
Closed

drop-packages: Cabal is silently ignored #5707

andreasabel opened this issue Apr 11, 2022 · 3 comments

Comments

@andreasabel
Copy link

Entry

drop-packages: 
- Cabal

in stack.yaml seems to be silently ignored.
So working around

according to the recipe in

fails.

@mpilgrem
Copy link
Member

I think that stack may not be ignoring drop-packages: - Cabal; I think that recent resolvers do not include Cabal to start with - so that it is the version of Cabal that ships with the version of GHC that is relevant. See commercialhaskell/stackage#4425 (comment) (from March 2020).

@mpilgrem
Copy link
Member

With my investigation above and the updating of the documentation, I am going to close this issue.

@andreasabel
Copy link
Author

Thanks for the explanation, @mpilgrem !

chreekat added a commit that referenced this issue Jan 8, 2024
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.
chreekat added a commit that referenced this issue Jan 8, 2024
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.
chreekat added a commit that referenced this issue Jan 8, 2024
As described in the resolution to #5707, Cabal is no longer included in
snapshots, so dropping it has no effect.
chreekat added a commit that referenced this issue Jan 8, 2024
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants