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:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=FQpdtVH
	LFycboJXVNqX9ELXq7fnwzyPn6tSgiFGULi38OmfXAEJBbytuCSni6XA7IyayNT1
	lRZMaScQZQxnagZ8p9dUMYFGtQ1IGcIRSvq+ty7JF4ARn8a74I2pd4yuIbaclQi5
	5nFCyT+T5TJ/7LFIBW7llYwId2prDjWwJhYs=
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:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; s=default; bh=6Y8qBAJOzIGiD
	KvVsPNtkRwRJAs=; b=hhtWOWPtQbmsW4OLGTu/kul9gPqz/qAX/cUPCKnBKJ6PD
	MYA3E9FtbLkGXYGDSdS0cEGHC0dN2oYC0C66h+jXV0dKdo5IDjuZaXtrnglbqmuf
	ZNMaUHmSVeSm/jNccDODZj05FaiT+CFCFE5uByJcIKZ0oht4y2ixM1qSR/WEv8=
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=-1.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=respectful, brianinglissystematicswabca, BrianInglissystematicswabca, Brian DOT Inglis AT systematicsw DOT ab DOT ca
X-HELO:	mail-it1-f173.google.com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=rERpBNXwAFS4BrUvzGWUFoFvmk2sliYK4ucywrPc4jk=; b=dZHYdq5W6QNNeoR0GkLTrEf4TL9Mbi20Ru1XpqqUd8omgAkEw4a12aGCbCEH01UbSM FS6o+LqSXlHWQv+LQgta1uQonNSoot6qyefpz7HtmnayVZSQUw5yBRPG3bJ/d+jz0e2a Lq4EP5nFOf6DKxG6d2oBpuHobXfw+oJsrzMt0Lcdir60stuZzlqdzLjUGQT1iE3iMs54 DXyuO521BV/plzv2W+o7o5cXd+6Qzp6KOVTG+en1EBKMKyUQAUZr5LjWOPC+mOnO9q1u 5Ag8Dvd66pncLVQFMTbefjmGZmOhAv8rau700Ir9Im4oIuMDzihM61FiQPgNsRLOAGbY SWgA==
MIME-Version:	1.0
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> <9e60d216-3e48-2f95-1bd9-b958b5265820 AT SystematicSw DOT ab DOT ca>
In-Reply-To:	<9e60d216-3e48-2f95-1bd9-b958b5265820@SystematicSw.ab.ca>
From:	Keith Christian <keith1christian AT gmail DOT com>
Date:	Wed, 12 Jun 2019 07:15:50 -0600
Message-ID:	<CAFWoy7F3r75OJxz9gaf2uO2Tas=tWgtNYB1fyf=5cv_4XmFaDw@mail.gmail.com>
Subject:	Re: setup.exe enhancement request, proceed on error after logging error to setup.log
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

Brian,

All-volunteer.  I understand that well, and have been using Cygwin for
a long long time.

The volunteers love what they do, and I try to be as respectful as
possible when suggesting changes, changes mean more work for them.

I'm satisfied with this thread.

Thanks Achim, Jon, and to any other setup maintainers, and to all
Cygwin maintainers for the selfless work you do.

Keith



On Wed, Jun 12, 2019 at 7:01 AM Brian Inglis
<Brian DOT Inglis AT systematicsw DOT ab DOT ca> wrote:
>
> 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
>

--
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

- Raw text -