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 15:55:15 +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 g4C5tN313480 > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Sunday, May 12, 2002 3:09 PM > To: cygwin-apps AT cygwin DOT com > Subject: Re: setup.exe updated > > > On Sun, May 12, 2002 at 12:58:21AM -0400, Christopher Faylor wrote: > >On Sun, May 12, 2002 at 12:55:48AM -0400, Christopher Faylor wrote: > >>I just noticed that the UCX compression breaks upset's ability to > >>detect the setup.exe version. So, it's still being reported as > >>2.194.2.26 in setup.ini. > >> > >>Is there any way to make UCX not compress the embedded > version string? > > > >%s/UCX/UPX/g > > Ok. Here's a possible solution for that: > > Don't compress setup.exe with upx. I've installed upx on > sourceware and it seems to be able to compress this file with > no problem. > > So, just upload an uncompressed file and let the upset > process compress it after it has determined the version number. > > That's one less step for you, Robert. Hopefully it is acceptable. Works for me (tm). The only nit being that snapshots will already be compressed, so I'll need a fresh copy to copy over... Rob