Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: What kind of executable is zcat? Crashes from cmd.exe From: Robert Collins To: cygwin@cygwin.com In-Reply-To: References: <6.0.1.1.0.20040212153628.0393dba8@127.0.0.1> <001e01c3f1b1$b93d3ed0$6401a8c0@RossLap> <20040212215929.GA19769@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-WU/o3SxMa60dOD053feu" Message-Id: <1076624097.1258.14.camel@localhost> Mime-Version: 1.0 Date: Fri, 13 Feb 2004 09:14:57 +1100 X-IsSubscribed: yes --=-WU/o3SxMa60dOD053feu Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2004-02-13 at 09:05, Igor Pechtchanski wrote: > AFAIK, setup has always behaved this way. It first uninstalls the old > versions of all packages being upgraded (that's how the old pdksh.exe got > unlinked), and then installs the new versions (creating new files, > essentially). It never did overwrite the file in-place. Changing this > will probably involve radical modifications to setup's internal logic. Not that big a change actually - we already have the concept of upgrading internally, it just needs to be taught that an upgrade isn't an uninstall + install, but rather an unpack followed by removing files no longer present in the package. Rob --=20 GPG key available at: . --=-WU/o3SxMa60dOD053feu Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAK/rhI5+kQ8LJcoIRAgC+AJ9DdQ36kwu3V6U0rfhTCShX6QS24gCfW6YW fJZLtzm0MqOutxDAghk/QAY= =f7a4 -----END PGP SIGNATURE----- --=-WU/o3SxMa60dOD053feu--