Hello,
I think it would be a good idea to split deliveries (golang binaries) from where locally built files gets stored. Right now it tries to build files into
~/.goenv/versions/1.23.12/go-build-host-host-cgo/
This makes it hard to manage goenv when using a bubblewrap container where you want to map in the shared executables into a build-environment as read-only.
A idea would be to split this so deliveries go into ~/.goenv/versions/ so that folder can be mounted read-only into the container and then use ~/.goenv/build//... for anything that requires write-permissions.
This would allow the reuse of go-binares between containers while also allowing each container have their own build-cache folder.
Just a rough idea of what i'm having some issues with at the moment. Not sure if this is some new behavior by goenv 3.x or if it's a golang behavior-change.
Hello,
I think it would be a good idea to split deliveries (golang binaries) from where locally built files gets stored. Right now it tries to build files into
~/.goenv/versions/1.23.12/go-build-host-host-cgo/
This makes it hard to manage goenv when using a bubblewrap container where you want to map in the shared executables into a build-environment as read-only.
A idea would be to split this so deliveries go into ~/.goenv/versions/ so that folder can be mounted read-only into the container and then use ~/.goenv/build//... for anything that requires write-permissions.
This would allow the reuse of go-binares between containers while also allowing each container have their own build-cache folder.
Just a rough idea of what i'm having some issues with at the moment. Not sure if this is some new behavior by goenv 3.x or if it's a golang behavior-change.