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 Date: Thu, 12 Feb 2004 17:17:20 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: What kind of executable is zcat? Crashes from cmd.exe Message-ID: <20040212221720.GE19915@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: <6.0.1.1.0.20040212153628.0393dba8@127.0.0.1> <001e01c3f1b1$b93d3ed0$6401a8c0@RossLap> <20040212215929.GA19769@redhat.com> <1076624097.1258.14.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1076624097.1258.14.camel@localhost> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin@cygwin.com On Fri, Feb 13, 2004 at 09:14:57AM +1100, Robert Collins wrote: >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. Another nice change would be to make setup's tar understand hard links. I think it treats them as a copy now, doesn't it? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/