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 Subject: RE: setup.exe updated MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 12 May 2002 13:36:06 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4C3a9L24566 > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Sunday, May 12, 2002 1:34 PM > To: cygwin-apps AT cygwin DOT com > Subject: Re: setup.exe updated > > > On Sun, May 12, 2002 at 01:07:23PM +1000, Robert Collins wrote: > >I've copied across the new setup. As there are no new > features (other > >than not crashing as much :}) I don't think this warrants an > >announcement. > > Does this version understand bzip2 files? It occurred to me > that I don't really have to change 'upset'. I can just run > bzip2 when upset completes successfully. No. Only HEAD understands setup.bz2. HEAD should get released in another 2-3 weeks. For backward compatability, and to allow folk to change over (as they do) bit by bit, I think we should have both the .ini and the .bz2 for a while. I gave a sample post-upset line to create the bz2 file in an earlier email. Rob