Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Thu, 2 May 2002 21:27:12 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: MD5 support Message-ID: <20020503012712.GA2732@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Fri, May 03, 2002 at 09:14:33AM +1000, Robert Collins wrote: > > >> -----Original Message----- >> From: Christopher Faylor [mailto:cgf AT redhat DOT com] >> Sent: Friday, May 03, 2002 9:13 AM > >> >If you've got the bandwidth and disk space... cool. I figured that a >> >single copy of setup.ini getting mirrored was a low-cost >> solution (vs a >> >completely separate site). >> >> By "site" I meant something besides sources.redhat.com that >> wouldn't rely on accessing a mirror site to be useful. > >Exactly. Actually, I decided to just creat a version of setup.exe (based on the setup200202 branch) which silently skips extra the md5 element in install: and source: tags. This version is now installed in /sourceware/ftp/anonftp/pub/cygwin. I also checked in my upset code, causing the last upset run to create a setup.ini with md5 stuff in it. So, if someone wants to try your new setup.exe snapshot they just have to run it and use the newest setup.ini, once it propagates to a mirror. It looks like I *just* missed a mirror run from mirrors.rcn.net. There is a new version of setup.exe on that site along with an old version of setup.ini. cgf