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 12:54:48 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: MD5 support Message-ID: <20020502165448.GA6064@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 Thu, May 02, 2002 at 05:41:59PM +1000, Robert Collins wrote: > > >> -----Original Message----- >> From: Christopher Faylor [mailto:cgf AT redhat DOT com] >> Sent: Thursday, May 02, 2002 2:05 AM > >> >> Ok. There is a setup-md5.ini in /sourceware/ftp/anonftp/pub/cygwin >> (home of setup.exe and setup.ini). I generated it against my >> local release directory so there may be some irregularities >> in things like sdesc/ldesc and some versions may be off. >> >> However, it is usuable as a proof of concept. > >Thank you. Is it ok with you if I call it setup.ini and put it in a dir >called test after inserting ../ in front of every instance of >'release/'? I guess so. I wonder if it would make sense to have a completely separate test site for this kind of thing so as not to have the mirrors update testing stuff and, more importantly, so that we can make changes in real time. cgf