MySQL Uses Microsoft's Open Source Software
EqualSlash writes "The Windows installer for the upcoming MySQL 4.1 release will be built using Microsoft's first ever open source project - Windows Installer XML toolset(Wix). According to an InternetNews report, they are using Wix to convert the MSI file designed using InstallShield into XML to achieve greater control over the installer. Of course, they are simply using it because it's Open Source (CPL license) and in good faith. Earlier this year, when Microsoft surprised everybody by releasing the Wix project under an open source license, some were cautious about using it, as the specific XML schema it uses might be patented just like the Office xml schema. Whatever.. Rob Mensching, Wix's lead developer, is very happy about MySQL choosing to use Wix for their installer."
Wait, so what you're implying is...
Someone open-sourcing something causes more people to use it?!?!?
If it weren't for the fact that this is MS's open source creation being used, this would not be news.
In any case, kudos to MySQL for taking the first step with Wix and to Microsoft for trying something they have otherwise sworn against.
Hopefully more people will use Wix, and most importantly, will modify it and contribute changes. That would be a nice way of showing MS just what open source can offer, something which everyone else seems to have figured out already.
..components as the Windows installer I don't mind; no, actually I am happy that even MS can contribute a bit to the open source world.
Simply because the whole MySQL project can't be taken down by MS even though they're using Wix. It's not important enough for the project's life, that's it!
By opening up the source and making it possible for OSS developers to use a high quality installer, Microsoft has shown that it realizes the importance of Open Source software to its user base.
Amazing magic tricks
I've been trying to get my feet wet with this WiX stuff, but really the documentation is extremely lacking.
it's open source, duh!
Why would you rather they don't use it? So Microsoft thinks open source is a failure and never again makes an open source project?
but that's their call. Surely, there must be other alternatives than using something from M$. It's an installer - can't they use Nullsoft or something else?
MSIs allow for easy installation of programs across entire Active Directory networks. Sure, you can do this with scripts and silent installs, but MSIs let you do interesting things like per-user installs that migrate to computers with their profiles. A good example of this is TortoiseSVN, which I can install only for myself on a computer on an AD network, and when I go to another lab computer and logon it'll automatically install and yet still be visible to only me.
There's also a Firefox bug that's requesting an MSI installation option (but I forget the URL). IIRC someone built an MSI package using WiX, and several people have stated that an MSI package is imperative for corporate deployment of Firefox.
So yeah, there are alternatives, but using MSIs do make things easier for some people, me included.
... Microsoft will add security and a lot of features to MS SQL Server replacing it by MySQL.
Apache already does release an MSI format package, maybe they, too, could convert to WiX.
And then, there's only PHP left, that should come in an MSI file, and all would be fine.
OSS programmers should realize how important the installation package is. Because with an intelligent enough package (MSIs for Win32, debs for Debian etc), it's no longer simply copying and possibly files, but real Software Management. This is going to open doors to the large companies.
And yes, I know, MSI is a Microsoft idea, but it does make sense. Any large customer nowadays wants all the software to be re-packaged in MSI format (hell, repackaging Oracle Client sucks, you can believe me!).
What's the problem with using an installer written by Microsoft if someone is already writing the software for the Microsoft Windows platform anyway? Doesn't make a big difference, if you ask me...
...has had this for a while already.
It is this patent waver as a requirement for distributing the software that makes the CPL incompatible with the GPL as it imposes additional restrictions on redistribution over the GPL. However I understand that the FSF is considering putting in a patent clause in the next version of the GPL which would both make the CPL compatible with the GPL and restrict possible patent abuse.
Assuming there aren't any overriding difficulties with patents or licence problems, this would absolutely ideal for deploying Mozilla Firefox and Thunderbird. One of the biggest issues holding Firefox back from enterprise deployment in MS shops is the fact that there's no MSI installer. This would allow it to be rolled out to all the desktops domain-wide via Group Policy and , as the installer tracks any changes made, it can be rolled-back/uninstalled or upgraded easily. All that would needed to add to that would be some basic properties (hopefully via GPOs also) to allow admins to customise & lock it down a little (say, auto-set the web proxy details), and it'd be perfect!
0 33
:)
In fact, after doing a quick search it looks like someone's already done it (don't know if it uses WiX, though it is mentioned in the Bugzilla listing):
http://forums.mozillazine.org/viewtopic.php?t=138
Superb! Finally a way to get rid of IE from the corporate desktops