On 9/14/2017 1:26 PM, Achim Gratz wrote:
Ken Brown writes:
What I've been struggling with, however, is the UI. But now that I
think about it, maybe it isn't that hard. It's just a matter of doing
something reasonable if the user unchecks "Accept default problem
solutions". I'll see what I can come up with.
Well, zypper pretty much just gives you a bunch of possible solutions
and asks you to select one if there is either more than one or the
otherwise preferred solution is blocked by a lock. There is always one
"break <whatever> package by doing <stuff>" down that list. You could
maybe offer something along those lines in the inevitable dialog box?
In the long run I think that's the way to go. But implementing that is
more work than I feel like doing at the moment. For now I've gone with
an approach that was easier to program, more like the current setup.exe.
If the solver finds problems (including missing dependencies), the
user has four choices on the Prerequisite page:
1. Click Back to go back to the Chooser page, with the Pending view
showing the solver's default solutions.
2. Click Next to accept the default solutions.
3. Uncheck the "Accept default solutions" box and click Next. If the
user dismisses the resulting warning, setup will go ahead and do what
the user requested.
4. Cancel.
Once the inevitable remaining bugs are fixed, I think we'll have a
setup.exe that's better than the current one, with possibilities for
further UI improvements along the lines you suggested.
Ken
