[PATCH setup 00/14] Use libsolv, solve all our problems... (WIP)
Tue Dec 5 17:36:00 GMT 2017
On 12/5/2017 9:32 AM, Jon Turney wrote:
> On 14/09/2017 21:46, Ken Brown wrote:
>> 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.
> Doing some testing of per-version requires, I've been looking at this
> page quite a bit.
> It seems we're missing something to actually apply the default solution,
> so "accept default solutions" makes no changes, at the moment. (looks
> like we have to do this ourselves with solver_take_solution() ?)
I'm not sure. I thought at some point I saw "accept default solutions"
do something, but there have been a lot of changes since then.
> Also, in the dependency problem report, we should identify which of the
> possible solutions is the default one, so it's clearer what "accept
> default solutions" is going to do.
More information about the Cygwin-apps