summaryrefslogtreecommitdiffstats
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
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>
-rw-r--r--documentation/dev-manual/start.rst7
1 files changed, 1 insertions, 6 deletions
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst
index 6cc0f3e9f3..d383169cda 100644
--- a/documentation/dev-manual/start.rst
+++ b/documentation/dev-manual/start.rst
@@ -228,12 +228,7 @@ particular working environment and set of practices.
228 used by developers in the same organization and share the same 228 used by developers in the same organization and share the same
229 source directories on their machines. 229 source directories on their machines.
230 230
231 - Set up a local :ref:`overview-manual/concepts:Hash Equivalence` server 231 - Set up a local :ref:`overview-manual/concepts:Hash Equivalence` server.
232 with :term:`BB_HASHSERVE` and :term:`BB_SIGNATURE_HANDLER`. A basic setup
233 would be::
234
235 BB_HASHSERVE = "auto"
236 BB_SIGNATURE_HANDLER = "OEEquivHash"
237 232
238 See the :ref:`overview-manual/concepts:Hash Equivalence` section of the 233 See the :ref:`overview-manual/concepts:Hash Equivalence` section of the
239 Yocto Project Overview and Concepts Manual for more details on the hash 234 Yocto Project Overview and Concepts Manual for more details on the hash