On 12/12/2017 10:06 PM, Vince Rice wrote: >> On Dec 12, 2017, at 6:12 PM, Steven Penny wrote: >> >> On Tue, 12 Dec 2017 08:04:09, Ken Brown wrote: >>> How can setup possibly automate this? It doesn't know where the corrupt >>> local tarball came from. For example, suppose you sometimes build packages >>> yourself for testing or debugging. You keep them in your local repository, >>> and you also upload them to a private repository on the internet so that >>> you can easily install them on a different computer. You make a change and >>> rebuild the package, but you forget to replace all copies of it. setup >>> can't know which version is the correct one. And it certainly shouldn't be >>> deleting your files because it thinks they're corrupt. >> >> No, this is not right. If you are building packages yourself, then you should >> have a custom setup.ini to match, example: >> >> http://matzeri.altervista.org/x86_64 >> >> so that in any case, setup.ini has the final say of what a correct archive >> is, >> via the SHA512. If a file in the local repo doesnt match either because: >> >> - file size 0 >> - file size less than proper size because of interrupted download >> - SHA mismatch because of custom build >> >> said file should be removed and redownloaded by setup.exe. if you are >> building >> custom archives, then you should also be making custom setup.ini. > > Where is that stated as a requirement? I don't see it anywhere, and I don't > agree that it should be one. Ken is correct on this, IMO.
Both are correct views of operation. Steve could provide patches to allow a toggle for which logic to use with the default being what occurs now. -- cyg 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
