After discussing with some people about the issue, it looks like .msi is the way to go, it’s the only missing bit to add value over the existing .zip from Tor and the gladewin32 releases. But I’ll need help with this task.
We need contributors!
Right now is really hard for me to run Windows, I can do it with VMware but the lack of ram on my laptop makes it hard to try some things without making the swap play break dance, and I cannot leave the native Linux session for more than a couple of minutes due to other reasons. So I need people familiar with development environments on Windows, and if possible some experience with WiX, the opensource .msi creator.
Another problem is that the .mo message catalogs format on Linux and Win32 is different. So internationalization is broken. I need to try some kind of fix that doesn’t break the jhbuild automation tool chain.
Well, let’s say that it’s the DEB/RPM of Windows, it handles version issues and it’s deployable on hundred of machines through Active Directory, it doesn’t solve the dependency issue, but you can bundle .msm, which is like a modular .msi, inside a .msi, which would make the release of third party apps easier. At the same time, it would make integration with Windows RADs easier too.
Why do you work on this if you don’t run Windows?
I want everyone to be able to do what I do, enjoy PyGTK, there are people that cannot choose their operating system, and at the same time, they would like to be able to write GUI apps easily. I want to remove this "Linux/*BSD/Solaris Users Only" advertise on the doors of the GNOME community.
At the same time, I find the current release process of GTK+ on windows obscure, due to lack of time on the people that are doing the releases already, a proper documentation of the process is hard to get and requires self made scripts. My will is to integrate everything in just a .jhbuildrc and a moduleset, so anyone can give it a try with familiar tools.