Skip to content

Solver can automatically suggest changes when there is an unresolvable conflict #1616

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
harendra-kumar opened this issue Jan 6, 2016 · 1 comment

Comments

@harendra-kumar
Copy link
Collaborator

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 .

@mgsloan
Copy link
Contributor

mgsloan commented Jan 8, 2016

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.

@mgsloan mgsloan added this to the P3: Optional milestone Jan 8, 2016
harendra-kumar added a commit to harendra-kumar/stack that referenced this issue Jan 19, 2016
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants