While looking a few different AI options, I thought perhaps Modules was the way to go for this structure. But, as pointed out in this thread, these apparently don't support one very particular feature my environment requires. In my case, the files in question are run-time files that are unfortunately not created by the application that relies on them, but they are used for long-term storage (SQLite3 DB files), so they must never be overwritten if they exist.
Thinking a bit more "out the box" here, the most versatile approach would be to have an "installation laucher" of sorts. Effectively an installer that has multiple imported installers that can be launched individually from an installer page with custom buttons.. Each of the bundled packages could store machine-specific installation info on the target machine, which the core installer could be designed to check for and react to accordingly (hide/show different options, update current configuration, etc.). However, this also seems like a lot of work in the setup stages, which makes me wonder if it's not perhaps going to create unnecessary work maintaining them down the line.. Nothing a few batch build files can't resolve, but again, more to maintain down the line.
Has anyone got any experience with multi-product installation packages like this..? I've pretty much been thrown in the deep end with installation package feature requests, so I'd really appreciate some suggestions / ideas for getting around this.
FOLLOW US
Get the latest news in Application Packaging