-
Notifications
You must be signed in to change notification settings - Fork 44
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
Software conflicts research #944
Software conflicts research #944
Conversation
|
||
1) Start by showing the dependency issue when selecting a pattern. | ||
2) Extend *yast-pkg-bindings* and improve the issue message, showing the details of the problems. | ||
3) Raise a question when the solver generates problems. This should be done for each call to the solver, not only for selecting patterns. |
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.
I still think that at least in some cases we should offer option to revert new selection to solve issue. Like you add qt..ok...you add gnome and get conflict with option revert that unselects gnome without too much thinking.
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.
Yes, I think it is doable for some cases. We could emit a first question for undo the change. If the question is canceled, then we emit a question for solving issues (or everything in the same question).
Anyway, I think it is something to evaluate when implementing it, but it would require nothing new from D-Bus or yast-pkg-bindings.
Problem
Software conflicts cannot be solved in Agama and we need to find out how to do it. This is specially evident when selecting incompatible patterns (e.g., KDE and Gnome in openSUSE MicroOS Desktop).
Solution
Create a research document pointing to how to notify and solve conflicts by using the questions mechanism.