DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:subject:to:references
	:content-type; q=dns; s=default; b=Sd/Fg+nLbeBX9FmxlRQGrDcH2bC8X
	rCFrn3Qr+MEgkLYgn5gqQ+meh5ys5E8PO3jfXm/zXFNAsryt/GBnaHDJF4q6Xlv7
	HAV0Gqcd8R6Zu6aqDAXMLairzZ9VYhOE7U/fKdmxqHDfo1ueuKHZvpNlPtjFWaYa
	Fu6Xfu8mvFvfVo=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5a331856.46e8ca0a.834c.f39b@mx.google.com>
Date: Thu, 14 Dec 2017 16:33:26 -0800 (PST)
From: Steven Penny <svnpenn AT gmail DOT com>
Subject: Re: setup's response to a "corrupt local copy"
To: cygwin AT cygwin DOT com
References: <b031c829-d3a0-f28e-9ce0-0052e7d3475a AT cornell DOT edu>
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.0.1 (github.com/svnpenn/tryst)

On Thu, 14 Dec 2017 14:57:14, Ken Brown wrote:
> And, as I said, it happens when setup is *preparing* to download files and
> finds a corrupt copy already present in the local cache. In that context,
> setup has no idea where the file came from.

the point is, *it doesnt matter*. it is not and shouldnt be setup.exe job to
worry about the origin of files in the Local Package Directory.

Officially this directory, and the files below, are only created by setup.exe
itself. If people are creating their own custom archives, then putting them in
the Local Package Directory, *then* expecting them to work without a modified
setup.ini, that is an error in judgment on their part.

my original point, and one that i stand by as ive seen no reasonable counter
yet, is that setup.exe should assume control of the entire Local Package
Directory and its contents. this includes removing rogue files that are in
conflict with the current setup.ini. As Hans said:

http://cygwin.com/ml/cygwin/2017-12/msg00126.html

my viewpoint would be in concert with a typical "Git" workflow:

1. make changes to working directory
2. add those changes to the index

with step 2 being the analogue to creating a custom setup.ini. setup.ini should
always have the final say on what a correct file is; so if you want a custom
archive then you better tell setup.ini about it or otherwise risk it being
nuked.


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