News for hackers. Stuff that matters.
Re:Problems with Go Get by barsonme on Thursday May 07, 2015 @10:57PM (#9509754)
Seriously. What I'd like from Go is a structure where there's a source directory for my libraries (including external), a directory for the produced binaries (if any), and a text file that describes all my dependencies (including version #s). Inside each library there could be a file that provides the version # of the library.

While building the program, Go should search in my $GOPATH for the specific libraries, and if they're not found, search the libraries included with my package.

Some of the issues they've talked about included, "What happens when you can't `go get` a library because internet dies/repository moved/etc.?", which IMO is a good reason to include the libraries _with_ your Go package.

Re:Problems with Go Get by threeseed on Friday May 08, 2015 @02:50AM (#9510320)
> What happens when you can't `go get` a library because internet dies/repository moved/etc.

You cache the libraries in a central repository like Nexus or Artifactory and back it up.

This is standard practice in enterprise development where everything is restricted from downloading software except for this particular server.