On Tue, 18 Nov 2025 at 16:55, Stephen Jolley via lists.openembedded.org <[email protected]> wrote: > We aim to build 5.3 when the remaining identified issues with bitbake-setup > are resolved: ... > Other potential changes that have been discussed but don’t have workable > patches yet: > > defaulting to a common sstate directory and hashequiv server
I looked into this a bit. The key question is how would the lifecycle of such a server be managed (e.g. what starts the server and what shuts it down, since we don't want to leave users with mysterious, dangling processes doing nothing). I think a workable approach would be this: - bitbake invocations would continue to start (and stop) private server processes that are accessed through a unix socket inside their respective build directories - such invocations would be configured to use a *shared* sqlite database that is inside bitbake-setup's top directory - sqlite documentation gives reassurances that this is okay: https://sqlite.org/faq.html#q5 An alternative would be to somehow manage a common, single server, but I just can't figure out how to do it automatically, and without fuss and complications. Something has to start it, something has to shut it down. It must be available when any bitbake invocation from any setup directory happens. Users should not have to issue special magic commands to make it work. I think sharing the database is far easier. So the particular nomenclature for this would be: BB_HASHSERVE = "auto-shared-database" (e.g. start and stop the server automatically, but configure it to use a common database file, unlike 'auto' which keeps the database private to a build directory) BB_HASHSERVE_SHARED_DB = "/path/to/common/hashserv.db" bitbake-setup would put this (and SSTATE_DIR) into site.conf that is symlinked into every build. Terrible idea? Tell me :) Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#226769): https://lists.openembedded.org/g/openembedded-core/message/226769 Mute This Topic: https://lists.openembedded.org/mt/116358332/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
