It would be nice to be able to lock specific recipes against changes when doing development work. This could be in the form of the bblock X and bbunlock X commands. The mechanism would use the locked-sigs mechanism which can be seen by: "bitbake bash -S none" then looking at the locked-sigs.inc file it generated. These are activated by including the inc file in local.conf. The lock/unlock commands would use entries of this syntax, probably in a separate file they could maniululate, included from local.conf. When locked sigs are in operation, a note to the user, similar to the way the "-f" taint files trigger notes to the user would be desirable.
*** Bug 6425 has been marked as a duplicate of this bug. ***
As a note, tinfoil would have APIs which could implement this (or we'd add them)
I hacked up this last week. https://github.com/rossburton/bb/blob/master/libexec/bb-lockdown basically uses -S to generate a locked-sigs.inc, removes the lines that we still want to rebuild, then writes an auto.conf to pull the file in.
Hi Richard, I can handle this Bug. But in what case do people need to lock a specific recipe?
Hi Richard, Ross, Do we create a new parameter for bitbake to do this feature? Or just a script same as Ross' one in poky/scripts ?
If for example someone wants to make changes to the rust recipe but doesn't want rust-native to rebuild every time, they only want to rebuild rust itself. In this case they would lock rust-native. I think this should be a separate tool and not an option to bitbake. We can use the tinfoil bitbake API if needed though.
Hi Duy, Richard and Ross, I would be happy to help on this. Duy did you make any progress on this?
I'm unaware of any progress beyond my scripts being a demonstration that the concept works.
Ok, so I'll take a look at this
Hi Julien, I'm busy recently and cannot handle it. So that's OK if you can take this bug
Bulk move to 4.3 M3.
Merged in 2d9ab0cfd7f3cacc347954676f1323342a6b286f.