<mark_weaver>piyo: I would try again now. if the problem persists, please let me know.
<taylan>I'm being told the normal way to do things in Go is that when your code contains e.g. import("github.com/foo/bar"), the build toolchain fetches the sources for that transparently. (I guess Go folks don't normally care much about building software in a restricted environment, dunno.)
<taylan>maybe we could create a "go-foo-src" package for each "go-foo" package, use such source packages as inputs to go packages, and arrange for the toolchain to use locally provided sources instead of fetching them.
<piyo>Okay for one thing I was routing http requests through Privoxy, which may have rewritten content (not good). Now that I am just rerouting through squid3 and I seem to be progressing with some guix pull halts. The current guix pull process seems to be downloading with no problems.
<taylan>the norm seems to be that your local directory hierarchy contains e.g. $workspace/src/my-app which is a git repo and then dependencies are put in $workspace/src/<dependency>, i.e. alongside the git repo that contains your app's source
<saml>Given, $workspace/src/project1, $workspace/src/project2@v1 and project1 depends on different version of project2, i put that in $workspace/src/project1/vendor/src/project2@v2 and prefix GOPATH with "$workspace/project1/vendor:$GOPATH" when i'm building project1