-
-
Notifications
You must be signed in to change notification settings - Fork 369
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
Remove dependency on Cabal #195
Conversation
Looks like stylish-haskell is pulling it in anyway to detect language extensions from the cabal file |
3206a72
to
b4db132
Compare
When I use I get the output:
I dont think it is that easy. EDIT: I think |
Yeah Setup.hs always depends on Cabal, but with the removal of cabal-helper in the near future(?) then that would leave us with just stylish-haskell as the sole user. In any case, we definitely don't need it in hls just to print a version string |
stack-8.10.1.yaml
Outdated
# - cabal-helper-1.1.0.0 | ||
- github: DanielG/cabal-helper | ||
commit: 79a5608778493bf32e74b54bbf1ea2729941e50f | ||
- Cabal-3.0.2.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we keep it here but remove it elsewhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This stackage snapshot contains to Cabal-3.2, others already contain Cabal-3.0.1, and stylish-haskell requires Cabal < 3.1
Cabal as a dependency is a pretty hefty price to pay for simply getting the build architecture, which already seems to be in System.Info. Probably just accidentally copied over from when HIE used Cabal for dealing with .cabal files
b4db132
to
993b59c
Compare
I just undid the stack.yaml changes, might as well get whatever's in 0.3.0.2 over 0.3.0.1 https://hackage.haskell.org/package/Cabal-3.0.2.0/changelog |
Cabal as a dependency is a pretty hefty price to pay for simply getting the build architecture, which already seems to be in System.Info. Probably just accidentally copied over from when HIE used Cabal for dealing with .cabal files