I would like to avoid another installation is running when starting an installation or an installation step


  • Currently, we are mimicking this by running an action checking for the presence of another possibly conflicting installation and writing to a signal file, which in turn is used in an action requirement. But this is ugly and cumbersome to maintain. Plus, it is not working well when trying to apply it to bundle requirements.