Say I wanted to use RoundhousE for my database deployment. I would like to be able to reference it as a dependent package. Then call for it to run as part of my deploy.ps1.
This is probably going to sit on the backlog for a while - dependent packages would need to be pushed to the Octopus, and they’d then be installed to different folders. Your Deploy.ps1 would have to use something like “…\MyDependency.\foo” to then get at the dependency contents. Packaging something like RoundhousE into your package (so it is self-contained) is the only way it works at the moment.
I’m not sure how common it is for these kinds of dependencies to come up in the wild, so I’m keen to see if anyone else would find this feature useful.