Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Subject: Re: 1.3.4 From: Robert Collins To: Charles Wilson Cc: cygwin-developers AT cygwin DOT com In-Reply-To: <3BE05ED8.7@ece.gatech.edu> References: <20011031113304 DOT A7957 AT redhat DOT com> <3BE05ED8 DOT 7 AT ece DOT gatech DOT edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.15 (Preview Release) Date: 02 Nov 2001 13:50:39 +1100 Message-Id: <1004669440.5558.41.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 02 Nov 2001 02:54:55.0380 (UTC) FILETIME=[C0576540:01C16349] On Thu, 2001-11-01 at 07:28, Charles Wilson wrote: > setup.exe (2.112): The current vs. new vs. prev vs. test detection > algorithm doesn't seem to work properly. (e.g. parsing > /etc/setup/installed.db and/or setup.ini) > > Setup.ini says > > @ ash > sdesc: "A Bourne Shell (/bin/sh) workalike" > category: Base Shells > requires: cygwin > version: 20011018-1 > install: latest/ash/ash-20011018-1.tar.bz2 33819 > source: latest/ash/ash-20011018-1-src.tar.bz2 143186 > [prev] > version: 20010827-1 > install: latest/ash/ash-20010827-1.tar.bz2 33780 > source: latest/ash/ash-20010827-1-src.tar.bz2 143017 > > When my current installation was 20010827-1 (according to > /etc/setup/installed.db) the latest setup was perfectly happy (that is, it > did not want to update ash). It just said: > 20010827-1 Keep That is a bug :}. It's the default logic code that is at fault (choose.cc, line 578). The code needs to allow installed packages to auto upgrade. > So, I clicked on the 'Keep' until it changed to '20011018-1' -- which had > the unfortunate side effect of reverting my "skipped" cygwin package to > 'I'm gonna install 1.3.3-2' (I had previously used setup to install my > custom cygwin-20011031 snapshot, and I wanted to stick with it for a > while). So I had to go click THAT to change it back to 'skip' That sounds like a dependency issue. So dependencies must not alter packages that 1) are installed 2) have any action other than uninstall. ... > Anyway, after rebooting, I tried again (without any active cygwin windows). > I let it do its thing (e.g install new ash, but let it also "update" > cygwin). I then reinstalled my custom cygwin snapshot. > > Finally, I ran setup AGAIN -- just to see what it would say about my "new" > ash-20011018-1. > > Again, it's happy. '20011018-1 Keep' > > It appears that setup is perfectly happy with WHATEVER version of a given > pacakge is already installed. The whole [test], [prev] and current thing > seems to be ignored. Rob