7 messages in com.mysql.lists.win32RE: Reasons for the MSI package to exist
FromSent OnAttachments
Daniel da Veiga11 Dec 2005 18:06 
Mike Hillyer11 Dec 2005 18:40 
Daniel da Veiga11 Dec 2005 19:36 
Armando12 Dec 2005 19:26 
Daniel da Veiga13 Dec 2005 09:34 
Bill Angus14 Dec 2005 09:14 
Daniel da Veiga14 Dec 2005 10:55 
Subject:RE: Reasons for the MSI package to exist
From:Mike Hillyer (mhil@mysql.com)
Date:12/11/2005 06:40:05 PM
List:com.mysql.lists.win32

Can anyone give me any good reason why is there an .MSI package with configuration wizard for MySQL? I understand the fact that msi is the default windows install way, and MySQL is always using standards, but thats not enough reason for me.

Why not use the standard? If every program out there uses an MSI (yes, a generalization), why not MySQL? MSI files can be easily embedded into other installers, making it easier to add MySQL to another application's installer.

As I see, the .msi, and specially the configuration wizard that comes with it, makes it more difficult for people to understand MySQL, because they think it is a program like any other, that you install, run, and everything is ok, and a database doesn't work like this.

Why shouldn't it? MySQL has long had a policy of being up and running within 15 minutes of the completion of a download, and having an easy to use installer helps meet this goal. I personally do not think the installation process should be a right of passage to use the software, so I am all for a tool that you install, run, and everything is ok.

IMHO, when people step into trouble using the Wizard, it makes them think is MySQL fault, while most problems are caused by the wizard itself.

Then let's fix the wizard.

The MSI is not mandatory, neither is the running of the configuration wizard after install. There is a NoInstall archive, and the box for running the config wizard can be unchecked.

I expect comments, not flames, thank you.

Hopefully you see that I intended to provide the former.