This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [PATCH setup 00/14] Use libsolv, solve all our problems... (WIP)
- From: Jon Turney <jon dot turney at dronecode dot org dot uk>
- To: cygwin-apps at cygwin dot com
- Cc: Ken Brown <kbrown at cornell dot edu>
- Date: Fri, 15 Sep 2017 16:15:42 +0100
- Subject: Re: [PATCH setup 00/14] Use libsolv, solve all our problems... (WIP)
- Authentication-results: sourceware.org; auth=none
- References: <20170531105015.162228-1-jon.turney@dronecode.org.uk> <488ba627-de58-ddc7-7f69-696adae76b8a@cornell.edu>
On 08/09/2017 19:54, Ken Brown wrote:
Finally, I have a question for you, Jon: You introduced
PrereqChecker::upgrade, which is true if and only if the user selects
Current or Test. I don't see why this is needed. I've disabled the use
of it and haven't noticed any ill effects. Am I missing something?
This is supposed to be passed into SolverSolution::update() and used to
determine if a SOLVER_UPDATE | SOLVER_SOLVABLE_ALL task is given to the
solver, causing all packages to be updated (if possible) (i.e. so 'Keep'
doesn't update anything)
I guess the UI could be improved to make the choice of 'Keep' or
'Current' ('Update') orthogonal to 'Use test packages?'