You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can automatically determine the minimal number of user packages to remove to be able to come up with a workable build plan. We can do this automatically when init/solver is used with --force and write the removed packages commented out in the config with an appropriate conflict reason comment. This allow diagnosing and fixing dependency problems quickly.
Makes sense! #1593 is also relevant, as otherwise you can't really select just the cabal files that are needed. Might be good to provide the commandline options along with the suggestion.
When there is an unresolved conflict among the dependencies of multiple source
packages then remove one of the conflicting packages and then retry. The
package chosen to be removed is the one which is on top of the dependency
pyramid i.e. noone else depends on it.
The functionality is not yet complete. It will be complete once cabal output is
parsed and the list of conflicting packages is fed to the upper level logic.
See commercialhaskell#1616
See #1583 (comment).
We can automatically determine the minimal number of user packages to remove to be able to come up with a workable build plan. We can do this automatically when init/solver is used with
--force
and write the removed packages commented out in the config with an appropriate conflict reason comment. This allow diagnosing and fixing dependency problems quickly.This will perhaps depend on #1615 .
The text was updated successfully, but these errors were encountered: