From: Ken Brown <kbrown@cornell.edu>
To: cygwin <cygwin@cygwin.com>
Subject: setup's response to a "corrupt local copy"
Date: Wed, 13 Dec 2017 14:36:00 -0000 [thread overview]
Message-ID: <b06765ec-3d9c-d52b-50c5-7ed22bbb8619@cornell.edu> (raw)
This is a followup to the discussion started here:
https://cygwin.com/ml/cygwin/2017-12/msg00088.html
When setup is preparing to download files and it finds a corrupt copy in
the local cache, it issues a fatal error message telling the user to
remove the corrupt file and retry. Steven said that setup should
silently delete the corrupt file, while I argued in favor of the current
behavior, on the grounds that setup shouldn't be deleting user files if
it doesn't know where they came from.
There is a middle ground: setup could query the user. Additionally, as
suggested by cyg Simple, there could be an option that directs setup to
silently remove corrupt files.
Ken
--
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 reply other threads:[~2017-12-13 13:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 14:36 Ken Brown [this message]
2017-12-14 4:40 ` Hans-Bernhard Bröker
2017-12-14 20:13 ` Andrey Repin
2017-12-14 23:34 ` Ken Brown
2017-12-15 13:05 ` Steven Penny
2017-12-15 14:53 ` Vince Rice
2017-12-16 7:52 ` Steven Penny
2017-12-16 14:40 ` Frank Redeker
2017-12-16 15:33 ` Vince Rice
2017-12-16 20:47 ` Steven Penny
2017-12-16 20:47 ` Ken Brown
2017-12-15 15:20 ` Andrey Repin
2017-12-16 4:00 ` Brian Inglis
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=b06765ec-3d9c-d52b-50c5-7ed22bbb8619@cornell.edu \
--to=kbrown@cornell.edu \
--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).