In the cases it's supposed to address, it does make a striking difference.
I interrupted a bulk build that was about 1000 packages along.
The I restarted it twice, once without -d, once with -d.
Without -d, there is a flat queue at start, and the jump when vars discovers
groff is striking.
With
Turns out the option is not really needed. There's no case where it's not
a good idea when starting a rebuild and using -a, and also the dependencies
file location is trivial to find, so just make it automatic and kill the
darn option...
with USE_GROFF around, it might be that, when you restart a failed dpb,
it will sit quite some time before it reaches some unbuilt port that doesn't
use dpb.
There's now a new file, dependencies.log, and a new option,
-d dependencies.log, to fix that issue: at the end of the dependencies walk,
d
