From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 72416 invoked by alias); 12 Jun 2019 13:01:00 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 72409 invoked by uid 89); 12 Jun 2019 13:01:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=installation X-HELO: smtp-out-no.shaw.ca Received: from smtp-out-no.shaw.ca (HELO smtp-out-no.shaw.ca) (64.59.134.12) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 12 Jun 2019 13:00:57 +0000 Received: from [192.168.1.114] ([24.64.172.44]) by shaw.ca with ESMTP id b2s2hS0ggsAGkb2s3h8GRO; Wed, 12 Jun 2019 07:00:55 -0600 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: setup.exe enhancement request, proceed on error after logging error to setup.log To: cygwin@cygwin.com References: <87muioniop.fsf@Rainer.invalid> <2e00e327-37d9-ded2-6c11-1d7ad3adf069@SystematicSw.ab.ca> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <9e60d216-3e48-2f95-1bd9-b958b5265820@SystematicSw.ab.ca> Date: Wed, 12 Jun 2019 13:01:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00137.txt.bz2 On 2019-06-11 14:52, Keith Christian wrote: > On Tue, Jun 11, 2019 at 12:39 PM Brian Inglis wrote: >> On 2019-06-11 11:19, Achim Gratz wrote: >>> Keith Christian writes: >>>> Would the maintainers (Achim? Jon?) be willing to consider an option >>>> box log errors to the setup.log file and "Skip non-fatal errors and >>>> continue?" >>> >>> You'd first have to teach setup to distinguish between fatal and >>> non-fatal errors. A missing package archive is always fatal as far as >>> setup is concerned (how did that happen anyway?). >> >> A mirror update failure, an unsafe mirror update process, or the latter leading >> to the former. > Thanks for the feedback. > > Even if a file were missing that might cause issues in a few > dependency chains, why not allow the install to continue? > > Suppose a file was missing halfway through? Why stop the whole > install for the sake of a few missing files? Let the install continue > for those packages that aren't missing files, write a message to the > log, and put up a dialog after both the successful installs and the > rebasing are done. User clicks OK and uses Cygwin in its current > state, or she/he restarts the install from a different mirror. Pick > up the missing files for the few packages and all done. > > This would ultimately save time and effort. > > Whatever the case, if a file is missing, setup will have to be run > again to fix the problems, by pointing to another mirror, etc. > > Thanks for listening. What it ultimately comes down to is this is a group of volunteers. None of them want to have to try to explain or fix a broken setup on a user's system caused by a broken mirror: they don't have the time. So if there is any chance of setup breaking an install, setup will quit before it does any damage. Whether setup lets you know in a dialogue box or in a log file, that it upgraded or failed to upgrade your installation, may depend on your install options. Personally, I would be very happy if setup popped up the setup log at the end of the run, if there were any issues. I have done this kind of results display in Windows and Unix command line and GUI environments for user and developer tools: launch a log viewer if there was a problem, launch an app if results are good. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple