I will try that out to see if I find a better way to handle it.
Regarding the deployment dependencies, yes, this is something I am planning to add in the environment XML file schema. It will then be possible then to specify the order how the solutions are deployed.
I am also thinking about allowing to specify optional custom targets for each wsp, so that one can run some scripts before continuing with the next wsp. Still have to come up with a good idea how to code it though. I don't want the environment xml to become
too complicated and unmanageable.
BTW, for general prerequisite solutions (which are not deployed through the package) you can specify them in the corresponding section of the environment xml.
helps you with that in case you don't want to mess around directly with the xml.
Looking forward to hear more feedback and ideas for improvement :-)