[bitbake-devel] [PATCH 1/2] bitbake: ensure -f causes dependent tasks to be re-run

[Björn Stenberg]

Paul Eggleton wrote:
> If -f is specified, force dependent tasks to be re-run next time. This
> works by changing the force behaviour so that instead of deleting the
> task's stamp, we write a "taint" file into the stamps directory, which
> will alter the taskhash randomly and thus trigger the task to re-run

I'm concerned about calling this -f/--force. I don't think I'm alone in interpreting -f / --force as "run all commands, even if the dependencies say we don't need to". I would expect the same output as the first time, with the same sstate checksum.

Would it be reasonable to call it something like -t/--taint instead?

-- 
Björn