X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=KhGSwu30Jj/gH9KT
	Dj2pIua2SK5RZyYjrUr5pUz3twRTxoTFS8PqWy5xAabfDoLmxBbeVYotegnHqzeL
	agQukrTIHusK6esHJjCniaUMslH4UTvYpWgHRb3gH35QXe5pOL41ud0gLhHvUXub
	pZNXokdW6PtfgF9rAbjnzeeZgAo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=YDScy3HvoyRihnqN7PwndP
	HKqW0=; b=khRQMqYgOvSok8JCrI6YbaLCp9RtzIxxdI3tQtQvur0ot0RYlSu7vz
	3L4hShf2gf68nCS6xKsJxVOxrJk0WXnf9XJOfbwzL547TZRvn5x1VdXsjQ12C4Vs
	VuvsHMSE+kMMbWEv8x2sfuEFqcv5Jfu+sq+ocohaQJQx5GW3Rn1tQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
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
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: setup.exe enhancement request, proceed on error after logging error to setup.log
To: cygwin AT cygwin DOT com
References: <CAFWoy7FT1T7v=WOvKNRpz7vryCZ0SvYYooDmzH_HU06igu-yhA AT mail DOT gmail DOT com> <87muioniop DOT fsf AT Rainer DOT invalid> <2e00e327-37d9-ded2-6c11-1d7ad3adf069 AT SystematicSw DOT ab DOT ca> <CAFWoy7EE8M8NbJ_cWkiux=6qUX0k84biwOweF_QNKti+q7Ox=A AT mail DOT gmail DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <9e60d216-3e48-2f95-1bd9-b958b5265820@SystematicSw.ab.ca>
Date: Wed, 12 Jun 2019 07:00:54 -0600
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: <CAFWoy7EE8M8NbJ_cWkiux=6qUX0k84biwOweF_QNKti+q7Ox=A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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