Excellent!
These days go has become much simpler to deal with (nearly any folder with
a go.mod is a go project) but legacy GOPATH things remain to confuse
matters.
When I'm at a computer I'll see how necessary that line was for beam go
development with that env script.
I'd run one of the
Woohoo it works! How could I forget the oldest trick in the book "just
delete the problematic line"
Thanks for the quick response. I am unblocked now :)
On Fri, Mar 22, 2024 at 8:47 AM Robert Burke wrote:
> It's not clear to me why that's even requesting that package at all. I
> would remove
It's not clear to me why that's even requesting that package at all. I
would remove that 'go get' line.
There's a different issue at play here too since it was written for
pre-module Go in mind. I'm unfamiliar with that script though.
I'll take a proper look in a few hours.
On Fri, Mar 22,
Hi,
I've been banging my head trying to get a dev environment working. I gave
up trying to get a local python environment working after I got some weird
clang errors and proto generation issues so I've been trying to just use
the docker container by running `bash start-build-env.sh` but I'm
