From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 121567 invoked by alias); 5 Dec 2017 14:32:52 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 121537 invoked by uid 89); 5 Dec 2017 14:32:50 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=struggling, asks, ui, offer X-HELO: out5-smtp.messagingengine.com Received: from out5-smtp.messagingengine.com (HELO out5-smtp.messagingengine.com) (66.111.4.29) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 05 Dec 2017 14:32:49 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 9110A217C9 for ; Tue, 5 Dec 2017 09:32:47 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 05 Dec 2017 09:32:47 -0500 X-ME-Sender: Received: from [192.168.1.102] (host86-179-113-49.range86-179.btcentralplus.com [86.179.113.49]) by mail.messagingengine.com (Postfix) with ESMTPA id 2FF1D7E56E for ; Tue, 5 Dec 2017 09:32:47 -0500 (EST) From: Jon Turney Subject: Re: [PATCH setup 00/14] Use libsolv, solve all our problems... (WIP) References: <20170531105015.162228-1-jon.turney@dronecode.org.uk> <488ba627-de58-ddc7-7f69-696adae76b8a@cornell.edu> <7a173f99-a2e1-a07c-a9df-5bebcf377957@cornell.edu> <87poau9znx.fsf@Rainer.invalid> <050204e5-0ed3-8e47-3825-58ec6a10f44f@cornell.edu> <87ingltcn0.fsf@Rainer.invalid> <4ed6c549-dddd-fc45-3ed8-f7339548d7cd@cornell.edu> To: cygwin-apps@cygwin.com Message-ID: Date: Tue, 05 Dec 2017 14:32:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <4ed6c549-dddd-fc45-3ed8-f7339548d7cd@cornell.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2017-12/txt/msg00019.txt.bz2 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 package by doing " 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() ?) 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. > 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.