Damn! Just as I thought we did a dot zero release without big problems…
Takashi attached couple of fixes to tracker items (installer fixes and search fix). These installer bugs are a real problem for me. How is it possible nobody noticed these in few experimentals, one beta and one release candidate release? And now we have a release which fails to install some important things properly.
I guess the only explanation is these problems happen only for new installs, not when updating WinMerge. And people who install non-stable releases usually are updating WinMerge. So one good lesson – make sure the first install works in addition to update. Not that it is hard to test – virtual machines make this easy and fast. Just need to remember it. (I added that ‘test the installer’ emphasis into the installer documentation…)
As bad as these bugs may sound like, I’m not ready to make a new release yet. Yes, they make first install look worse. But there is no lost functionality or data. User can fix the situation pretty easily.
Once again a good lesson how fragile these Windows program installers are. Even though Innosetup is a lot less fragile than some other systems, it is still way too easy to mess up the installer. You just have to know what things to install for group or common and what to current user. And perhaps the only way to know is by try and error?
We need somebody more familiar with installers to improve WinMerge installer…
