Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com, chris Subject: Re: Wishlist additions for setup.exe Reply-To: sds AT gnu DOT org X-Attribution: Sam X-Disclaimer: You should not expect anyone to agree with me. Mail-Copies-To: never From: Sam Steingold In-Reply-To: <40853C12.3070507@cs.york.ac.uk> (chris's message of "Tue, 20 Apr 2004 16:04:50 +0100") References: <150840-220044220121135845 AT cantv DOT net> <1082472769 DOT 4984 DOT 4 DOT camel AT localhost> <40853C12 DOT 3070507 AT cs DOT york DOT ac DOT uk> Mail-Followup-To: cygwin AT cygwin DOT com, chris Date: Tue, 20 Apr 2004 12:54:05 -0400 Message-ID: User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain > * chris [2004-04-20 16:04:50 +0100]: > > Personally I would perfer a system where the setup program simply kept > a central cache, rather than a seperate cache for each mirror Indeed! While I can easily think of some reasons to keep per-mirror caches (e.g., what if the mirrors are out of sync?) it is certainly bad UI to make the user aware of this, even indirectly. If you really need per-mirror caches, you can hide them from the user and always scan all of them. This will always be faster than downloading the same file anew. BTW, what's the policy about the older package tarballs? Are they ever removed? (it appears so...) -- Sam Steingold (http://www.podval.org/~sds) running w2k If you want it done right, you have to do it yourself -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/