`run` silently accepts and stores non-portable in/output specs
mih opened this issue · comments
This is a threat to portability of run-records, and users are not made aware.
I believe, at minimum, run should warn when it sees such declarations. User may be feeding the output of scripts to build such declarations, and may not be aware.
It may be difficult to perform automatic conversions in the general case, but at least the documentation should make very clear that only relative paths are exploiting the full potential of this machinery.
Might be worth adding some --mode flexible,strict (flexible is current default) so in --mode strict it would error out if inputs or outputs do not match... or alternatively --strict {inputs|outputs|both} analogous to --expand and --assume-ready we have