From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
<alex.kanavin@gmail.com>
Cc: <docs@lists.yoctoproject.org>,
"Matthias Schiffer" <matthias.schiffer@ew.tq-group.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 2/4] ref-manual/structure.rst: update with info on PERSISTENT_DIR
Date: Tue, 15 Jul 2025 09:05:53 +0200 [thread overview]
Message-ID: <DBCFSE5GDADI.263HWWQM1LUHQ@bootlin.com> (raw)
In-Reply-To: <ca38bde3e186f7ff5ba3e290e49bc80cbf2df4d7.camel@linuxfoundation.org>
On Fri Jul 11, 2025 at 11:45 PM CEST, Richard Purdie wrote:
> On Fri, 2025-07-11 at 19:09 +0200, Alexander Kanavin via lists.yoctoproject.org wrote:
>> On Wed, 9 Jul 2025 at 09:57, Antonin Godard via lists.yoctoproject.org
>> <antonin.godard=bootlin.com@lists.yoctoproject.org> wrote:
>> >
>> > Since we mention that SSTATE_DIR can be shared for multiple builds, also
>> > mention that PERSISTENT_DIR should be shared alongside SSTATE_DIR.
>>
>> NO. These changes are incorrect, please do not merge or revert if
>> already merged.
>>
>> PERSISTENT_DIR can be copied from one build directory to another when
>> bitbake is not running, but it cannot be shared between two active
>> builds.
>>
>> If one wants to share sstate, they either have to setup a hash
>> equivalence server (and then sharing PERSISTENT_DIR is not needed), or
>> disable hash equivalency (in which case it is also not needed).
>
> The changes did merge and definitely are unclear.
>
> The point is that if you share sstate, you also need to have common
> hash equivalence data.
>
> That may be via having common hashequiv server, or, of you have a local
> sstate directory and delete the build directory, you need to preserve
> the hashequiv database file to make the sstate useful.
>
> You cannot have a common PERSISTENT_DIR shared by two builds, that is
> not supported.
>
> Hopefully Antonin can tweak things to make this all clearer. I should
> have caught this, sorry :/
Hi all,
Sorry! I drew a wrong conclusion from bug #15921, I will correct this soon
this week.
Alex, thanks for catching this.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-07-15 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 7:57 [PATCH 0/4] Improvements around PERSISTENT_DIR Antonin Godard
2025-07-09 7:57 ` [PATCH 1/4] test-manual/understand-autobuilder.rst: mention hashequiv server Antonin Godard
2025-07-09 7:57 ` [PATCH 2/4] ref-manual/structure.rst: update with info on PERSISTENT_DIR Antonin Godard
2025-07-11 17:09 ` [docs] " Alexander Kanavin
2025-07-11 21:45 ` Richard Purdie
2025-07-15 7:05 ` Antonin Godard [this message]
2025-07-09 7:57 ` [PATCH 3/4] dev-manual/start.rst: mention that PERSISTENT_DIR should be shared too Antonin Godard
2025-07-11 17:13 ` [docs] " Alexander Kanavin
2025-07-09 7:57 ` [PATCH 4/4] overview-manual/concepts.rst: mention PERSISTENT_DIR for user configuration Antonin Godard
2025-07-11 17:14 ` [docs] " 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=DBCFSE5GDADI.263HWWQM1LUHQ@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=richard.purdie@linuxfoundation.org \
--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.