Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: MD5 support
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Wed, 1 May 2002 18:42:46 +1000
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5F67@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g418gtX29885



> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com] 
> Sent: Wednesday, May 01, 2002 2:35 AM

> I have upset ready to go for this.  Will it actually break 
> setup.exe if I check in my changes?  I'm away from a Windows 
> system right now so I can't check myself.

It will cause parsing errors, so even though setup is (somewhat)
resilient, it will generate questions.

If you could get upset to make a ini in a new location (perhaps test)
that refers to the release directory source files, that would be a great
test, and let me be sure that nothing will go ... wrong.

ie:

/setup.ini
/release/.....
/test/setup.ini <-- this contains MD5 information.

Can this be done?

Rob