Go Modules: Difference between revisions
| Line 28: | Line 28: | ||
=Module Path= | =Module Path= | ||
A module path serves as import path prefix for its packages. It also indicates where the [[#Go_Tool#Overview|<code>go</code> tool]] command should look to download it. For example, to download the module <code>golang.org/x/tools</code>, the <code>go</code> tool should go to the repository indicated by https://golang.org/x/tools. | A module path serves as import path prefix for its packages. It also indicates where the [[#Go_Tool#Overview|<code>go</code> tool]] command should look to download it. For example, to download the module <code>golang.org/x/tools</code>, the <code>go</code> tool should go to the repository indicated by https://golang.org/x/tools. | ||
=Module Proxy Server= | =Module Proxy Server= | ||
Revision as of 20:57, 7 September 2023
Internal
TO PROCESS
To process:
Overview
A module is a collection of related packages that are released, versioned and distributed together.
Packages are published as modules.
The module contains the packages in the directory containing its go.mod file as well as subdirectories of that directory, up to the next subdirectory containing another go.mod file (if any).
Modules may be downloaded directly from version control repositories, or from module proxy servers.
Declaring Modules
Building Modules
Publishing Modules
Consuming Modules
go.mod
go.mod declares the module path, which is the import path prefix for all packages within the module.
Module Path
A module path serves as import path prefix for its packages. It also indicates where the go tool command should look to download it. For example, to download the module golang.org/x/tools, the go tool should go to the repository indicated by https://golang.org/x/tools.