I've been playing with the go/build package for resolving go package information for a few projects of mine and noticed some unexpected behavior.
mainly it seems to reach out to the network even when all the information is available locally. if I turn off my network my code fails whereas go install seems to continue to function normally even without a network. is there a better way to resolve go packages locally than `build.Import(...)`? importer looks promising but it seems that it is currently impossible to provide a build.Context to an importer because the srcimporter is inside an internal package. https://github.com/golang/go/blob/master/src/go/importer/importer.go#L65 -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/0f620046-1f51-44bc-bc3d-0c017c7d97ben%40googlegroups.com.
