How to avoid hashing conflicts of build and consumed artifacts?

[kinderlars]

Hi,

I am currently encountering a few caching issues (hashes cannot be found (was xxx) kind of thing) with poetry, due to building a shared library on the same machine as where I consume it in another project (through remote artifact store).
It took me a while to figure out, that clearing the cache in the consuming project poetry cache clear . --all was only half the truth, but that I needed to remove the directory ~/Library/Caches/pypoetry/artifacts as well.

Now my idea is to isolate the build projects poetry from using the default caching directory.
My first attempt on setting the cache-dir went sideways, as I did not understand that it changes poetry globally and venvs not being created due to virtualenv: error: argument dest: the destination . is not write-able at /.

Never the less, how can I avoid caching/artifacts conflicts in poetry when building and consuming on the same machine?
Is there a recommended way to isolate a single project from using the default caching dir?

Update:
I was able to solve it for a build project by adding the POETRY_CACHE_DIR environment variable to my makefile.

PWD := $(shell pwd)
export POETRY_CACHE_DIR := $(PWD)/caches/pypoetry

For a global change, I saw the option of setting virtualenvs.in-project.