From: Keith Christian <keith1christian@gmail.com>
To: cygwin@cygwin.com
Subject: Re: setup.exe enhancement request, proceed on error after logging error to setup.log
Date: Tue, 11 Jun 2019 20:52:00 -0000 [thread overview]
Message-ID: <CAFWoy7EE8M8NbJ_cWkiux=6qUX0k84biwOweF_QNKti+q7Ox=A@mail.gmail.com> (raw)
In-Reply-To: <2e00e327-37d9-ded2-6c11-1d7ad3adf069@SystematicSw.ab.ca>
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.
On Tue, Jun 11, 2019 at 12:39 PM Brian Inglis
<Brian.Inglis@systematicsw.ab.ca> 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.
>
> --
> 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
next prev parent reply other threads:[~2019-06-11 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 21:41 Keith Christian
2019-06-11 8:03 ` Henning
2019-06-11 11:28 ` Keith Christian
2019-06-11 15:24 ` Brian Inglis
2019-06-11 16:35 ` Andrey Repin
2019-06-11 17:19 ` Achim Gratz
2019-06-11 18:39 ` Brian Inglis
2019-06-11 20:52 ` Keith Christian [this message]
2019-06-12 13:01 ` Brian Inglis
2019-06-12 13:16 ` Keith Christian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFWoy7EE8M8NbJ_cWkiux=6qUX0k84biwOweF_QNKti+q7Ox=A@mail.gmail.com' \
--to=keith1christian@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).