On Thu, Dec 17, 2009 at 02:12:15PM +0100, Corinna Vinschen wrote: >On Dec 16 13:40, Christopher Faylor wrote: >> On Wed, Dec 16, 2009 at 06:18:38PM +0100, Corinna Vinschen wrote: >> >But we discussed this on the developers list. The old setup will be >> >setup-legacy.exe and setup.exe is only for 1.7 and later. I'm rather >> >puzzled that you want to change this again. I have matching local >> >changes to the web page waiting. Please don't change this again. >> >> Since I have to change source code to understand the "release-legacy" >> directory, I opted to just do it in the trunk rather than the ancient >> setup 1.5 branch. There will still be a setup-legacy binary. > >Ok. The problem is just this. If setup.exe still works for 9x users >and just access setup-legacy.ini, they will never see that they are >accessing an unsupported repository. That's why I now think that >setup.exe should give them a warning instead. They should explicitely >be forced to use setup-legacy.exe if they updated at all.
"There will still be a setup-legacy binary" != "setup.exe will seem to work just fine for Windows 9x users". cgf
