Forcing Dependencies

To force a dependency that is not a "runtime dependency" you can include "Sticky" dependencies to your flow description. Since all jobs require at least one output to be valid, using sticky is a good way to keep a dependency around without having to instrument it or declare it as an output during execution of the job.

Example:

J vw cp aa bb
I -sticky /usr/man/man1/cp.1

To force all dependencies to be sticky by default, use the option -s in vovbuild when building the flow:

% vovbuild -s -f Flow.tcl