1 of 1 people found this helpful
i haven't tried anything like that but i fear that putting both in the same package just inflates the package size that must be pushed to the agent.
you'll end up trasferring 4x bytes to a server that will use only one installer out of the 4 availables.
is it worth?
My intent would be to have two separate packages -- each package containing the 32-bit and 64-bit version. I understand that it would inflate the overall size a bit, but it would still be manageable. (We actually have some single packages for other software that would be larger still.)
The other difference (the reason for an additional two source packages) is the target drive/directory, which is outside of our control. But I figured at least there may be some way to bundle the different platforms into one package, since BL can tell the difference on a given server. I know the 64-bit version will not install on a 32-bit machine, so I could just set the package to install both and rely on the install source to fail on an improper platform, but that seems a bit sloppy. Also, I'm not sure that a 32-bit install would fail on a 64-bit machine, so that might muck things up unnecessarily.