For Windows there is also the free Inno Setup (which I like because it's scriptable.) If this is a "mandate from on high" then get "on high" to fork out the cash for InstallShield.
For Linux there is also Autopackage. I can't speak much about it though.
Personally (on Windows) I use a combination of Makefiles and Inno Setup. After creating an installation script with Inno Setup, make release will bundle everything together and run the Inno Setup script packaging everything into a single installer executable. | [reply]
[d/l] |
I have a not dissimilar situation, I have a client who is totally Windows & PHP but they do run Apache on Intranet servers in about 30 locations. So we have done a NSIS (Nullsoft Installer which is highly scriptable and well supported) installer that ultiamtely runs a Perl programme (created with ActiveState's PerlApp) that re-configures the appropriate parts of the Apache config (There are modules that will read and manipulate Apache configs), then we install the main Perl prog also using ActiveState's PerlApp, but this time it unpacks itself and leaves it's mess behind - configuring things in such a way that the normal Apache CGI calls will work, the using Win32::Service we restart the Apache and away we go.
It's not really rocket science, but it does take a lot of time. And given that we have found the average Windows admin knows precious little about his machine we have found the totally automated way to be best. I set up a duplicate fo their system here to test it, and we haven't skipped a beat in the field - every one has installed correctly.
jdtoronto
| [reply] |