You really shouldn't need that at all once fleet is working as planned - you'd define a service which has the other service as a dependency, and that would delay starting until it's ready. 

One would hope that you don't need to ever block in a client-side script. We're doing this workaround because `X-Depends`/`X-After` doesn't yet exist in fleet. Those would allow us to do this orchestration fleet-side, and have it start the services whenever their dependencies are ready.