Kristen Kozak
Kristen Kozak
Currently cabal generates the summarized solver log by rerunning the dependency solver and having it prefer goals from the first run's final conflict set. The final conflict set may not...
Tests of the solver's current "rejecting" message would help us track progress on #4251. These tests could go in [cabal-install/tests/UnitTests/Distribution/Solver/Modular/Solver.hs](https://github.com/haskell/cabal/blob/master/cabal-install/tests/UnitTests/Distribution/Solver/Modular/Solver.hs), where we already have tests for other messages, such as...
The fetch command prints dependency solver errors in quotes: ``` $ cabal fetch cabal-install-99 Warning: this is a debug build of cabal-install with assertions enabled. Resolving dependencies... Error: [Cabal-7065] "Could...
As a step towards #4251, we could simplify the case where the solver rejects all instances of a package, such as when the index is not up to date. Here...
Hackage shows deprecated and preferred versions on each package page, but it seems to combine the two types of version ranges in the package index. This means that cabal can't...
@phadej and @gbaz suggested removing preferred versions in #1345, so I'm opening a new issue to discuss whether the feature is still needed. Is there a use case for preferring...
This idea was inspired by @georgefst's [comment](https://github.com/haskell/cabal/issues/10470#issuecomment-2422208659) in #10470. The solver currently stops searching as soon as it finds one solution. That solution maximizes each of the variables (package versions,...
This can cause the build to fail when the `setup-depends` range for Cabal is less restrictive than the `cabal-version` for a given package. See https://github.com/haskell/cabal/pull/3723#issuecomment-243337073. The current behavior is technically...
I don't think there is a clear design for component-based solving yet, so I wanted to create an issue where we can discuss it. #1575 addresses circular dependencies in test...