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 From: "Hannu E K Nevalainen" To: Subject: RE: Wishlist additions for setup.exe Date: Tue, 20 Apr 2004 21:18:11 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In-Reply-To: > From: Sam Steingold > Sent: Tuesday, April 20, 2004 6:54 PM > > * 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...) To get some "help": Google for the latest "clean_setup.pl". I have the script below for a standard run of it... note: /install -> place for setup.exe "local package dir" -- clean_install_dir -- #!/bin/bash #This is a shell for the clean_setup.pl script ( echo -e "\n\n-- "; date +"$0 run at %F %H:%M %z"; echo -e "\n"; clean_setup.pl -DDir -MFile -keepold -archive OLD-downloads $* ) \ \ | tee -a /install/clean_setup.log -- eof -- /Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E ** on a mailing list; please keep replies on that particular list ** -- printf("LocalTime: UTC+%02d\n",(DST)? 2:1); -- --END OF MESSAGE-- -- 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/