On Sat, 19 Nov 2016 09:09:14 -0800 Howard Howell <hlhowell@xxxxxxxxxxx> wrote: I don't use go, but thought I'd look at this. > So the current issue is where can I find the code.google.com > go packages? Any idea? > >From this page, https://golang.org/doc/articles/go_command.html, the following excerpt seems to suggest that you use go itself to install those commands and libraries. Just a thought. """ Here’s an example. Let’s say we decide to keep our Go code in the directory $HOME/mygo. We need to create that directory and set $GOPATH accordingly. $ mkdir $HOME/mygo $ export GOPATH=$HOME/mygo $ Into this directory, we now add some source code. Suppose we want to use the indexing library from the codesearch project along with a left-leaning red-black tree. We can install both with the "go get" subcommand: $ go get code.google.com/p/codesearch/index $ go get github.com/petar/GoLLRB/llrb $ Both of these projects are now downloaded and installed into our $GOPATH directory. The one tree now contains the two directories src/code.google.com/p/codesearch/index/ and src/github.com/petar/GoLLRB/llrb/, along with the compiled packages (in pkg/) for those libraries and their dependencies. Because we used version control systems (Mercurial and Git) to check out the sources, the source tree also contains the other files in the corresponding repositories, such as related packages. The "go list" subcommand lists the import paths corresponding to its arguments, and the pattern "./..." means start in the current directory ("./") and find all packages below that directory ("..."): $ go list ./... code.google.com/p/codesearch/cmd/cgrep code.google.com/p/codesearch/cmd/cindex code.google.com/p/codesearch/cmd/csearch code.google.com/p/codesearch/index code.google.com/p/codesearch/regexp code.google.com/p/codesearch/sparse github.com/petar/GoLLRB/example github.com/petar/GoLLRB/llrb $ We can also test those packages: $ go test ./... ? code.google.com/p/codesearch/cmd/cgrep [no test files] ? code.google.com/p/codesearch/cmd/cindex [no test files] ? code.google.com/p/codesearch/cmd/csearch [no test files] ok code.google.com/p/codesearch/index 0.239s ok code.google.com/p/codesearch/regexp 0.021s ? code.google.com/p/codesearch/sparse [no test files] ? github.com/petar/GoLLRB/example [no test files] ok github.com/petar/GoLLRB/llrb 0.231s $ If a go subcommand is invoked with no paths listed, it operates on the current directory: $ cd $GOPATH/src/code.google.com/p/codesearch/regexp $ go list code.google.com/p/codesearch/regexp $ go test -v === RUN TestNstateEnc --- PASS: TestNstateEnc (0.00 seconds) === RUN TestMatch --- PASS: TestMatch (0.01 seconds) === RUN TestGrep --- PASS: TestGrep (0.00 seconds) PASS ok code.google.com/p/codesearch/regexp 0.021s $ go install $ """ _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
