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: Sat, 11 May 2002 23:47:12 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: setup.exe updated Message-ID: <20020512034712.GA4955@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 Sun, May 12, 2002 at 01:36:06PM +1000, Robert Collins wrote: > > >> -----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. Actually, I intend to have setup.ini and setup.bz2 pretty much forever. I don't think there is any harm in keeping both around. It will certainly make upset processing faster and eliminate (or postpone indefinitely) the need for upset to understand compressed setup.ini files. cgf