Re: [PATCH setup 00/14] Use libsolv, solve all our problems... (WIP)

[Ken Brown <kbrown@cornell.edu>]

On 9/27/2017 3:14 PM, Jon Turney wrote:
> On 26/09/2017 17:06, Ken Brown wrote:
>> On 9/26/2017 10:50 AM, Jon Turney wrote:
>>> On 15/09/2017 17:53, Ken Brown wrote:
>>>> On 9/15/2017 11:15 AM, Jon Turney wrote:
> [...]
>>> If we select 'curr', then the latest version of all installed 
>>> packages is selected by the picker and will be shown in the pending 
>>> view, and gets fed into the solver.
>>>
>>> I guess this is technically wrong: really we should ask the solver to 
>>> do SOLVER_UPDATE | SOLVER_SOLVABLE_ALL, which will come up with a 
>>> solution which updates all installed packages to the latest possible 
>>> version, subject to any other constraints which exist.
>>>
>>> I suspect there's no difference between these two at the moment, though.
>>>
>>> Not sure how to do this properly, though.
>>
>> One possibility is that we feed all our information to the solver 
>> before going to the chooser page.  We could then present the solver's 
>> initial solution in the pending view as the first thing the user sees.
> 
> Yes, this sounds about right.
> 
> Thanks to your work we kind of have a bidirectional conversion between 
> packagedb pick/desired state and a SolverTransactionList now, so this 
> should be possible.
> 
> (Although it should be done when the state of the 'Keep' or 'Current' 
> control changes - note that changing this setting clears any manual 
> picks currently. [and there's a mechanism to apply the initial state of 
> that control initially])

OK, I'll work on this.  I'm traveling at the moment, but I should be 
able to do it in a couple weeks.

Ken