Sometimes you just want to build an individual recipe or task whilst still taking care of dependencies, but not being concerned if one has changed signature. For example, if you force rebuild the kernel currently anything that depends on the kernel rebuilds as well, which is usually unnecessary if you're just working on a part of the kernel and not changing any of the ABI that those other recipes care about (which would probably be most of the time). We could look at adding the ability to build an individual task/tasks in isolation without worrying about whether other tasks have changed hashes ("uncached mode" as Richard describes it ?) as a way to solve this.
Still a good idea.
You can do this today with bitbake -b. Another option is locked signatures which also gives a mechanism to do this although without a good UI. A rough possible UI type workflow could be: bitbake-lock lock * bitbake-lock unlock bash bitbake bash or similar. The backend mechanism exists but the UI tooling does not.
Marking this one as a duplicate of bug 13425 since we've solidified our idea around how this should work there. *** This bug has been marked as a duplicate of bug 13425 ***