From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Alexander Kanavin" <alex.kanavin@gmail.com>
Cc: <docs@lists.yoctoproject.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Matthias Schiffer" <matthias.schiffer@ew.tq-group.com>
Subject: Re: [docs] [PATCH 2/2] dev-manual/start.rst: remove shared PERSISTENT_DIR mentions
Date: Wed, 16 Jul 2025 09:28:07 +0200 [thread overview]
Message-ID: <DBDAVYFTZ6JV.2TSQDQCH9NU87@bootlin.com> (raw)
In-Reply-To: <CANNYZj_kvLsZG3sgH+nPu9B=pqWBU785w0SGHGdQqB4UW-DtmA@mail.gmail.com>
On Tue Jul 15, 2025 at 5:55 PM CEST, Alexander Kanavin wrote:
> On Tue, 15 Jul 2025 at 11:56, Antonin Godard via
> lists.yoctoproject.org
> <antonin.godard=bootlin.com@lists.yoctoproject.org> wrote:
>
>> + - Set up a local :ref:`overview-manual/concepts:Hash Equivalence` server
>> + with :term:`BB_HASHSERVE` and :term:`BB_SIGNATURE_HANDLER`. A basic setup
>> + would be::
>> +
>> + BB_HASHSERVE = "auto"
>> + BB_SIGNATURE_HANDLER = "OEEquivHash"
>
> This is still problematic and should be clarified further:
>
> 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.
>
> Maybe it's easier to just remove the above, and only refer to the hash
> equiv section in the other manual:
>
> + - Set up a local :ref:`overview-manual/concepts :Hash Equivalence` server
> +
> + See the :ref:`overview-manual/concepts:Hash Equivalence` section of the
> + Yocto Project Overview and Concepts Manual for more details on the hash
> + equivalence feature.
>
> Then we can do a correct, comprehensive description there.
Yes, I also feel that hash equivalence could deserve its own document, and
should go further than a server/client local to the build directory only. Thanks
for the clarification.
I will try to work on this soon, at least for now the shared PERSISTENT_DIR
mention is reverted, which is good.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-07-16 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 9:56 [PATCH 0/2] Remove shared PERSISTENT_DIR mentions Antonin Godard
2025-07-15 9:56 ` [PATCH 1/2] ref-manual/structure.rst: remove " Antonin Godard
2025-07-15 9:56 ` [PATCH 2/2] dev-manual/start.rst: " Antonin Godard
2025-07-15 15:55 ` [docs] " Alexander Kanavin
2025-07-16 7:28 ` Antonin Godard [this message]
2025-07-16 8:44 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DBDAVYFTZ6JV.2TSQDQCH9NU87@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.