summaryrefslogtreecommitdiffstats
path: root/documentation/sphinx-static
diff options
context:
space:
mode:
authorAntonin Godard <antonin.godard@bootlin.com>2025-07-16 11:10:07 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-08-01 11:59:18 +0100
commit6e5d021cd6f80401978fd018554cfb891e8fd43b (patch)
tree4069980754e1ccf8df6ad4d8fb667f075d0f5287 /documentation/sphinx-static
parent237c6b629aaa2f0f42fe8f2dfec5701ce3020dc8 (diff)
downloadpoky-6e5d021cd6f80401978fd018554cfb891e8fd43b.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: 231fc9e710ab34db60263f8ae01d4f5970579203) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/sphinx-static')
0 files changed, 0 insertions, 0 deletions