Joel Sing wrote: > Thanks for clarlifying - we could still implement 'go get -d' as a way > of getting sources, but it would be more work than it is likely worth > (and there are also some issues surrounding which versions of the > dependencies get fetched). > > I'll rework go.port.mk and the relevant packages using > /usr/local/go-pkg.
Just to clarify, is /usr/local/go-pkg (or whatever else we end up calling the dir) going to be added to the default $GOPATH as a patch? Will it be suggested to the user in a post-install message? Or is this only for the port system, and users won't have access to the port dependencies?