-
Notifications
You must be signed in to change notification settings - Fork 697
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
Update cabal-install-solver synopsis (fix #10183) #10192
Conversation
I wonder if we can say more, like why it's separate. I think someone said they were using a different solver locally, and this made it easier to swap solvers out? |
@geekosaur good point. That's below my pay grade, sadly. We'd need someone with better understanding of things to phrase it carefully.. @grayjay, would you be interested in putting together a couple of sentences about the mission and potential use cases of cabal-install-solver as a separate package? We could put them in the package description. Currently it's pretty low on content... |
@mergify backport 3.12 |
✅ Backports have been created
|
Oh, I forgot about it completely! Setting the label... |
I thought you were waiting for @grayjay to comment. |
I think it's too simple of a change to bother Kristen. But there is a two-day delay still! |
Sorry I missed this. I'm not very familiar with the decision to split the solver into another package. It's possible that the same goal could be met by moving it into a sub-library within cabal-install, though I don't know whether cabal-install can use the sub-libraries feature yet. I do know that cabal-install-solver currently doesn't have a stable interface. I think that it would take some work to turn it into a library that could be easily depended upon. For example, the solver unit tests test the solver through an interface that is still part of cabal-install. |
* Update cabal-install-solver synopsis (fix haskell#10183) * fixup! remove trailing dot --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: