The default signature handler has changed from 'OEBasic' to 'OEBasicHash'. But in the ref manual, 'OEBasic' is still said to be the default. " OE-Core uses the "OEBasic" signature handler by default through this setting in the bitbake.conf file: BB_SIGNATURE_HANDLER ?= "OEBasic" "
Indeed, I just noticed this also. We probably need to extend this section to mention the PR server for 1.4 as well.
Here is the updated section; ----------------------------------- The rules for deciding which hashes of dependent tasks to include through dependency chains are more complex and are generally accomplished with a python function. The code in meta/lib/oe/sstatesig.py shows two examples of this and also illustrates how you can insert your own policy into the system if so desired. This file defines the two basic signature generators OE-Core uses: "OEBasic" and "OEBasicHash". By default, there is a dummy "noop" signature handler enabled in BitBake. This means that behavior is unchanged from previous versions. OE-Core uses the "OEBasicHash" signature handler by default through this setting in the bitbake.conf file: BB_SIGNATURE_HANDLER ?= "OEBasicHash" The "OEBasicHash" BB_SIGNATURE_HANDLER is the same as the "OEBasic" version but adds the task hash to the stamp files. This results in any metadata change that changes the task hash, automatically causing the task to be run again. This removes the need to bump PR values and changes to metadata automatically ripple across the build. Currently, this behavior is not the default behavior for OE-Core but is the default in poky. ---------------------------------------------- Paul - if you could provide some information on how to extend this for PR server I can get that in. Thanks, Scott
Now that we have a separate section on the PR Service that is in the dev-manual, I provided a bit of cross-referencing between that new section and the area in the ref-manual that deals with "signatures" and the "shared state cache." This should satisfy tieing together the PR Service to the related areas in the ref-manual. I am marking this closed.