The new Go version 1.11 introduced the modules concept which is awesome.
In the documentation it says there are four directives that can be used in a go.mod
file: module
, require
, exclude
, replace
.
It also explains that:
exclude and replace directives only operate on the current (“main”) module. exclude and replace directives in modules other than the main module are ignored when building the main module. The replace and exclude statements therefore allow the main module complete control over its own build, without also being subject to complete control by dependencies.
But I still don't understand how the exclude
directive works.
Can someone explain to me how the exclude
directive works and if possible give an example of when to use it?
The go. mod file includes an explicit require directive for each module that provides any package transitively imported by a package or test in the main module. (At go 1.16 and lower, an indirect dependency is included only if minimal version selection would otherwise select a different version.)
The go mod vendor command constructs a directory named vendor in the main module's root directory that contains copies of all packages needed to support builds and tests of packages in the main module. Packages that are only imported by tests of packages outside the main module are not included.
The go mod init command creates a new module rooted at the current directory. A new go. mod file is created in the current directory; it must not already exist. The module path is the prefix path that is used to import all packages of that module.
Here's a semi-hypothetical hypothetical example:
module github.com/example/project
require (
github.com/SermoDigital/jose v0.0.0-20180104203859-803625baeddc
github.com/google/uuid v1.1.0
)
exclude github.com/SermoDigital/jose v0.9.1
replace github.com/google/uuid v1.1.0 => git.coolaj86.com/coolaj86/uuid.go v1.1.1
In the case of the github.com/SermoDigital/jose
package, it has a proper git tag for v0.9.1
, but the current version is v1.1
, which is NOT a proper git tag (missing the "patch" version).
By excluding the properly-versioned (but not working) code it causes go mod to fetch from master
instead (which is not properly versioned, but has the working code).
Likewise (and truly hypothetical), if I have a patch to github.com/google/uuid
, I can create a fork and use replace
to get my own version while I wait for the upstream version to accept my patch (or not).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With