Skip to content

Add 'BB_HASHSERVE_DB_DIR' to environment variables - #185

Open
ArtemMartus wants to merge 1 commit into
siemens:nextfrom
ArtemMartus:kas-bb-hashserve-db-dir
Open

Add 'BB_HASHSERVE_DB_DIR' to environment variables#185
ArtemMartus wants to merge 1 commit into
siemens:nextfrom
ArtemMartus:kas-bb-hashserve-db-dir

Conversation

@ArtemMartus

Copy link
Copy Markdown

[PATCH] kas: add BB_HASHSERVE_DB_DIR to allowed environment variables

Kas allows SSTATE_DIR to be set via an environment variable, but the latest oe-core will now warn if hashequiv has been enabled[1], the sstate is outside the build tree, but the hashequiv database is inside the build tree. This is because the hashequiv data is needed to make full use of the sstate objects.

The solution here is to also set the hashserver database location, but this can't be done in the same way as SSTATE_DIR as we can't set it as an environment variable. Add BB_HASHSERVE_DB_DIR to the list of variables that can be set in the environment so that callers can set them both if needed.

Kas allows SSTATE_DIR to be set via an environment variable, but the
latest oe-core will now warn if hashequiv has been enabled[1], the
sstate is outside the build tree, but the hashequiv database is inside
the build tree. This is because the hashequiv data is needed to make
full use of the sstate objects.

The solution here is to also set the hashserver database location, but
this can't be done in the same way as SSTATE_DIR as we can't set it as
an environment variable. Add BB_HASHSERVE_DB_DIR to the list of
variables that can be set in the environment so that callers can set
them both if needed.
@fmoessbauer

Copy link
Copy Markdown
Member

The ML thread somehow slipped through (I gave some feedback but did not receive a v2). I'll add the missing part and re-send it.

@jan-kiszka

Copy link
Copy Markdown
Collaborator

For reference: https://groups.google.com/g/kas-devel/c/4qTEgLffL3M
Will likely become part of the next release now.

@jan-kiszka
jan-kiszka force-pushed the next branch 10 times, most recently from e31ee61 to 263f3a3 Compare August 21, 2026 21:15
@jan-kiszka
jan-kiszka force-pushed the next branch 16 times, most recently from 32a6835 to 6dc1639 Compare August 23, 2026 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants