Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <F76C9B2DA2FC4C4CA0A18E288BBCBCF70361F1DE@nihexchange24.nih.gov>
From: "Buchbinder, Barry (NIH/NIAID)" <BBuchbinder AT niaid DOT nih DOT gov>
To: cygwin AT cygwin DOT com
Subject: RE: What kind of executable is zcat? Crashes from cmd.exe
Date: Thu, 12 Feb 2004 17:52:13 -0500
MIME-Version: 1.0
Content-Type: text/plain
X-IsSubscribed: yes

A suggestion for another setup feature:

When upgrading package foo requires reinstallation of package bar
afterwards, figuring that out and then doing it.

Thanks for all the good work.

- Barry

-----Original Message-----
From: Robert Collins [mailto:rbcollins AT cygwin DOT com] 
Sent: Thursday, February 12, 2004 5:15 PM
To: cygwin AT cygwin DOT com
Subject: Re: What kind of executable is zcat? Crashes from cmd.exe

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

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.

--
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/