Mail Archives: cygwin-developers/2001/11/01/21:47:11
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
- Raw text -