On Sat, 6 Dec 2025 at 04:31, Daniel Chaves <[email protected]> wrote: > Hi, Alexander, I saw your question about integrating the hash equivalence > server setup into Bitbake Setup. I've have actually tinkered with the basic > hash equivalence setup, and after diving into the documentation for the hash > equivalence looks like we could share hash equivalence data through following > the "Hash Equivalence Server Setup" instructions here: > https://docs.yoctoproject.org/dev/_sources/dev-manual/hashequivserver.rst.txt. > > Look at the `bind` and `database` options used when starting > `bitbake-hashserv`. Then, on the client side, the configuration would look > something like this: > > ``` > BB_HASHSERVE = "<bind address of the running BitBake hash server>" > BB_SIGNATURE_HANDLER = "OEEquivHash" > ``` > > So, in that scenario the site.conf for Bitbake Setup could enable a bind > address of `unix://${TOPDIR}/../hashserv.sock` to the BB_HASHSERVE. > > And the server can be started with something like: > > `bitbake-hashserv --bind unix://${TOPDIR}/../hashserv.sock --database > ${TOPDIR}/../hashserv.db`
Hello Daniel, the mechanics of configuring and starting the server are not the problem. The problem is how to do it in bitbake-setup workflows such that users don't need to know or care: no separate configuration, separate commands or leftover background processes. It should just work, quietly and without fuss. I have some ideas (around sharing the database between servers started privately by bitbake invocations (if BB_HASHSERVE is "auto")), just need to sit down and write patches. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#66097): https://lists.yoctoproject.org/g/yocto/message/66097 Mute This Topic: https://lists.yoctoproject.org/mt/116641652/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
