This is the mail archive of the
mailing list for the Cygwin project.
setup's response to a "corrupt local copy"
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin <cygwin at cygwin dot com>
- Date: Wed, 13 Dec 2017 08:28:00 -0500
- Subject: setup's response to a "corrupt local copy"
- Authentication-results: sourceware.org; auth=none
This is a followup to the discussion started here:
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple