"bob.mcwhirter" wrote :
| It's still a bootstrap scanner iterating deploy/'s children before deployers/
has been fully install, I think. Having scan() wait at a barrier of some sort until the
DEPLOYERS phase is complete would seem a possible solution.
So, if I understand this correctly,
we have another 1-time-only boot scan.
And it's before DEPLOYERS phase?
I need to check this, as it's clearly wrong,
for obvious reasons - for one this suffix case.
View the original post :
Reply to the post :