- Installer 1 is a standalone set of software
- Installer 2 has Installer 1 as a feature-based prereq
- Installer 3 has Installer 2 as a feature-based prereq
When I run Installer 3, it starts its prereq (Installer 2), which in turn launches its prereq (Installer 1). In this context, Installer 2 doesn't appear to wait for Installer 1 to finish. The log timestamps show that Installer 2 continues on while Installer 1 runs. Installer 1 eventually finishes successfully, but its parent (Installer 2) fails because it is dependent on Installer 1.
I assume that something is going wrong due to the fact that I have the installers nested like this. Is there any way to force Installer 2 to wait for Installer 1 in the scenario I described? Is there another reason that would cause this to happen?