[Offer] Windows Installer (MSI) Package for FileZilla

[Panarchy]

Good Evening,

I've recently figured out how to create MSI Packages, and as a personal challenge, would like to create an MSI Package for FileZilla.

However first I'll need a couple of questions answered;

• • Would you like an MSI Installer?
  • Is there any demand for an MSI Installer?
  • If I create an MSI Installer, will you include it on the SourceForge Project and FileZilla pages?

Regards,

Chip D. Panarchy

[botg]

I don't like MSI, those installers are damn slow. In the time it takes to merely load an MS installer, an NSIS based installer can run start to finish a dozen times.

Also, can you create MS Installers on Linux?

[Panarchy]

Hi botg,

Yes, that is one of the drawbacks of MSIs, another drawback is that it's compression isn't as good as NSIS.

However, a very big advantage of Windows Installer packages are that they can be deployed through Group Policy over an Active Directory domain.

I'm not suggesting to stop using NSIS, I'm merely imploring you to include 2 Installers, one for Administrators and one for End Users.

I'm happy to create the one for Administrators.

Regards,

Panarchy

[botg]

Also, can you create MS Installers on Linux?

[Panarchy]

If you are asking whether or not it'll work within WINE, it has achieved Silver;
http://appdb.winehq.org/objectManager.p ... n&iId=7911

However FileZilla is cross-platform, so I wouldn't see too much need to use it under WINE.

Although, if you are looking for someone to package it into .RPM & .DEB, then I may be able to, but first I want to perfect my Windows Installer skills.

Best regards,

Panarchy

[botg]

No, I mean can you create the MS Installer under Linux.

[eyebex]

Also take a look at these earlier discussions:
http://trac.filezilla-project.org/ticket/2613
http://forum.filezilla-project.org/view ... f=2&t=2153

[Panarchy]

No, I mean can you create the MS Installer under Linux.

With Virtualisation, or maybe WINE

However, why would you want to compile from Linux?

You'd have to test the installer on Windows anyway...

Panarchy

[botg]

Because of the automated build system. To create a release is a task of 10 seconds and everything gets built automatically. The Windows version of FileZilla is getting cross-compiled on Linux. Just need to wait a bit after starting the process and eventually everything will be built. Testing comes afterwards once everything has been built. Following testing, publishing a release is also a task of 10 seconds.

[Panarchy]

That does bring up an interesting point.

It takes 20 seconds to compile MSIs, even on Windows (1GB of RAM)

You could release everything but the MSIs, then I'll give you an MSI (or you can compile it) and post it 2 minutes later.

Panarchy

[botg]

There's another problem with the .msi, FileZilla has to be able to detect how it has been installed so that the update wizard downloads the right installer.

[Panarchy]

Shouldn't be too hard to implement, what with GUIDs and all.

[botg]

Can you please provide the necessary patches?

[Panarchy]

Sure.

Since it's just an offer, there's no rush to complete it, right?

(Just working on my CCNA & MCSA, so maybe Mid-January I'll be free to edit the code?)

Packaging isn't too difficult, it's just when I need to get down & dirty with TLS and upgrade codes...

Although, with MSIs, the main purpose would be to have the same version over the network, so the administrator would upgrade them all in one fell swoop, instead of through the built-in update engine.

I'm happy to fix the update eventually, but that does defeat part of the purpose of using Centralised Software Deployment solutions.

Panarchy

[botg]

Yes, no rush, take your time to make it perfect.