public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: setup's response to a "corrupt local copy"
Date: Sat, 16 Dec 2017 07:52:00 -0000	[thread overview]
Message-ID: <5a349a58.0a66ca0a.570e8.714d@mx.google.com> (raw)
In-Reply-To: <94A36026-06D9-4BD2-BFC5-68D5005D0071@solidrocksystems.com>

On Fri, 15 Dec 2017 09:50:44, Vince Rice wrote:
> It's my computer. I don't want setup (or anything else) replacing files on it
> it doesn't know about without at least asking whether that's what I want it to
> do. Setup's current behavior is exactly what it should be, IMO. If, as has
> been mentioned, someone wants to offer an *option* to replace, either with or
> without a question, then great. But the default should be to leave something
> it doesn't know about alone.

Thankfully we dont need your opinion on this matter, as we can simply fall back
to facts, as I will now do. Let us bring some sanity to this thread, shall we?

Exhibit A
====================
Package manager: APT
Reference distro: Lubuntu http://lubuntu.me
Cache: /var/cache/apt

Exhibit B
====================
Package manager: DNF
Reference distro: Fedora http://spins.fedoraproject.org/lxde
Cache: /var/cache/dnf
Option: keepcache=True

Exhibit C
=====================
Package manager: ZYpp
Reference distro: Gecko LXQt http://geckolinux.github.io
Cache: /var/cache/zypp
Option: --keep-packages

In all cases, these package managers remove invalid archives without warning.
Why should setup.exe be any different? I eagerly await your referenced and
reasoned rebuttal.

Cheers


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

  reply	other threads:[~2017-12-16  4:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 14:36 Ken Brown
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 [this message]
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=5a349a58.0a66ca0a.570e8.714d@mx.google.com \
    --to=svnpenn@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).