Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #574
Difficulty: Medium
The process of allocating and deallocating memory is generally referred to as memory swapping.
True or False?
Linux & Unix Commands - Search Man Pages

go-packages(7) [debian man page]

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

NAME
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 'code.google.com/p/project'. 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 <stapelberg@debian.org>, for the Debian project (and may be used by others). 2012-05-13 GO-PACKAGES(7)

Check Out this Related Man Page

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

NAME
go - tool for managing Go source code SYNOPSIS
go clean [-i] [-r] [-n] [-x] [ packages ] DESCRIPTION
Clean removes object files from package source directories. The go command builds most objects in a temporary directory, so go clean is mainly concerned with object files left by other tools or by manual invocations of go build. Specifically, clean removes the following files from each of the source directories corresponding to the import paths: _obj/ old object directory, left from Makefiles _test/ old test directory, left from Makefiles _testmain.go old gotest file, left from Makefiles test.out old test log, left from Makefiles build.out old test log, left from Makefiles *.[568ao] object files, left from Makefiles DIR(.exe) from go build DIR.test(.exe) from go test -c MAINFILE(.exe) from go build MAINFILE.go In the list, DIR represents the final path element of the directory, and MAINFILE is the base name of any Go source file in the directory that is not included when building the package. OPTIONS
-i The -i flag causes clean to remove the corresponding installed archive or binary (what 'go install' would create). -n The -n flag causes clean to print the remove commands it would execute, but not run them. -r The -r flag causes clean to be applied recursively to all the dependencies of the packages named by the import paths. -x The -x flag causes clean to print remove commands as it executes them. For more about specifying packages, see go-packages(7). AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others). 2012-05-13 GO-CLEAN(1)

Featured Tech Videos