I'm not going to remove this warning (it's bad form to do this), but in may cases it's difficult or even impossible to avoid. And seeing warnings every time you build leads to bad habits (ignoring them).
Perhaps the warning can be suprressed when we have stored dependency information for foo, and the builder file has not been modified since last build. That should catch most cases where you're doing it wrong, but will skip the warning whenever you (probably) haven't introduced that problem.
Alternatively, the build could declare itself to be a bad citizen by running gup --im-going-to-overwrite-my-target-directly. but that's ugly, and not very efficient.
I'm not going to remove this warning (it's bad form to do this), but in may cases it's difficult or even impossible to avoid. And seeing warnings every time you build leads to bad habits (ignoring them).
Perhaps the warning can be suprressed when we have stored dependency information for
foo, and the builder file has not been modified since last build. That should catch most cases where you're doing it wrong, but will skip the warning whenever you (probably) haven't introduced that problem.Alternatively, the build could declare itself to be a bad citizen by running
gup --im-going-to-overwrite-my-target-directly. but that's ugly, and not very efficient.