summaryrefslogtreecommitdiffstats
path: root/documentation/conf.py
diff options
context:
space:
mode:
authorAntonin Godard <antonin.godard@bootlin.com>2025-07-16 11:10:07 +0200
committerSteve Sakoman <steve@sakoman.com>2025-08-04 09:12:24 -0700
commitb13e4549a0be60d5c94e28da2ab386bef2f4bfc1 (patch)
tree7b9e9397ed8003d83c027a6fae1f3f8f919ca8d1 /documentation/conf.py
parent5f382d6f05870438611e6a4d9404078bb2e1639e (diff)
downloadpoky-b13e4549a0be60d5c94e28da2ab386bef2f4bfc1.tar.gz
dev-manual/start.rst: remove basic setup for hash equivalence
Quoting Alexander Kanavin [1]: > 1. BB_HASHSERVE and BB_SIGNATURE_HANDLER do not set up or start a > server, they set up the hash equivalence client built into bitbake. > > 2. The above client configuration (used by poky) also starts a private > server that is specific to a particular build directory. So hash equiv > information would not be shared between multiple build directories, > and this will cause sstate mismatches (as reported in the bug), if > sstate is shared. This setup does not shed light on the potential of the hash equivalence feature. So for now, remove this basic setup, and later rework the concepts (or create a new) document that explains how to set up a hash equivalence server shared between builds. [1]: https://lore.kernel.org/r/CANNYZj_kvLsZG3sgH+nPu9B=pqWBU785w0SGHGdQqB4UW-DtmA@mail.gmail.com Suggested-by: Alexander Kanavin <alex.kanavin@gmail.com> (From yocto-docs rev: 71c8b839e2621a048361d5518104099fee0f9e52) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> (cherry picked from commit 231fc9e710ab34db60263f8ae01d4f5970579203) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'documentation/conf.py')
0 files changed, 0 insertions, 0 deletions