Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #519
Difficulty: Easy
3,201 = 0b110010000001
True or False?
Linux & Unix Commands - Search Man Pages

go-packages(7) [bsd man page]

GO-PACKAGES(7)						 Miscellaneous Information Manual					    GO-PACKAGES(7)

go - tool for managing Go source code DESCRIPTION
Many commands apply to a set of packages: go action [packages] Usually, [packages] is a list of import paths. An import path that is a rooted path or that begins with a . or .. element is interpreted as a file system path and denotes the package in that directory. Otherwise, the import path P denotes the package found in the directory DIR/src/P for some DIR listed in the GOPATH environment variable (see 'go help gopath'). If no import paths are given, the action applies to the package in the current directory. The special import path "all" expands to all package directories found in all the GOPATH trees. For example, 'go list all' lists all the packages on the local system. The special import path "std" is like all but expands to just the packages in the standard Go library. An import path is a pattern if it includes one or more "..." wildcards, each of which can match any string, including the empty string and strings containing slashes. Such a pattern expands to all package directories found in the GOPATH trees with names matching the patterns. As a special case, x/... matches x as well as x's subdirectories. For example, net/... expands to net and packages in its subdirectories. An import path can also name a package to be downloaded from a remote repository. Run 'go help remote' for details. Every package in a program must have a unique import path. By convention, this is arranged by starting each path with a unique prefix that belongs to you. For example, paths used internally at Google all begin with 'google', and paths denoting remote repositories begin with the path to the code, such as ''. As a special case, if the package list is a list of .go files from a single directory, the command is applied to a single synthesized pack- age made up of exactly those files, ignoring any build constraints in those files and ignoring any other files in the directory. AUTHOR
This manual page was written by Michael Stapelberg <>, for the Debian project (and may be used by others). 2012-05-13 GO-PACKAGES(7)

Check Out this Related Man Page

GO-GET(1)						      General Commands Manual							 GO-GET(1)

go - tool for managing Go source code SYNOPSIS
go get [-a] [-d] [-fix] [-n] [-p n] [-u] [-v] [-x] [ packages ] DESCRIPTION
Get downloads and installs the packages named by the import paths, along with their dependencies. When checking out or updating a package, get looks for a branch or tag that matches the locally installed version of Go. The most important rule is that if the local installation is running version "go1", get searches for a branch or tag named "go1". If no such version exists it retrieves the most recent version of the package. OPTIONS
-a, -n, -v, -x, -p The -a, -n, -v, -x, and -p flags have the same meaning as in 'go build' and 'go install'. See go-build(1). -d The -d flag instructs get to stop after downloading the packages; that is, it instructs get not to install the packages. -fix The -fix flag instructs get to run the fix tool on the downloaded packages before resolving dependencies or building the code. -u The -u flag instructs get to use the network to update the named packages and their dependencies. By default, get uses the network to check out missing packages but does not use it to look for updates to existing packages. For more about specifying packages, see go-packages(7). For more about how 'go get' finds source code to download, see go-remote(7). SEE ALSO
go-build(1), go-install(1), go-clean(1). AUTHOR
This manual page was written by Michael Stapelberg <>, for the Debian project (and may be used by others). 2012-06-15 GO-GET(1)

Featured Tech Videos