Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

buildGoPackage: disable go module #73380

Merged
merged 2 commits into from Dec 10, 2019
Merged

buildGoPackage: disable go module #73380

merged 2 commits into from Dec 10, 2019

Conversation

marsam
Copy link
Contributor

@marsam marsam commented Nov 14, 2019 •
edited

Motivation for this change

Go 1.13 slightly changed the behavior GO111MODULE=auto [1], which might
accidentally cause the go command to build the module, for instance in
the checkPhase.

[GO111MODULE=auto] activates the module-aware mode of the go command
whenever the current working directory contains, or is below a
directory containing, a go.mod file — even if the current directory
is within GOPATH/src.

[1] https://golang.org/doc/go1.13#proxy-vars

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @ehmry @lethalman

@marsam marsam mentioned this pull request Nov 14, 2019
Merged
10 tasks
@jonringer
Copy link
Contributor

that's a lot of rebuilds, staging would be more appropriate

@marsam
buildGoPackage: disable module-mode
f1b7c83 
Go 1.13 slightly changed the behavior GO111MODULE=auto [1], which might
accidentally cause the go command to build the module, for instance in
the checkPhase:

    [GO111MODULE=auto] activates the module-aware mode of the go command
    whenever the current working directory contains, or is below a
    directory containing, a go.mod file — even if the current directory
    is within GOPATH/src.

[1] https://golang.org/doc/go1.13#proxy-vars
@marsam
documize-community: remove module-mode environment variable
87aec65 
We disable module-mode in buildGoPackage
@marsam marsam changed the base branch from master to staging November 14, 2019 11:31
@marsam marsam force-pushed the disable-buildGoPackage-module branch from b58fc48 to 87aec65 Compare November 14, 2019 11:31
@marsam
Copy link
Contributor Author

marsam commented Nov 14, 2019

Thanks for the heads up, moved base branch to staging

@fpletz
Copy link
Member

fpletz commented Nov 14, 2019

Does this change break builds with older Go versions?

@marsam
Copy link
Contributor Author

marsam commented Nov 14, 2019

It shouldn't, prior to Go 1.13, GO111MODULE=auto does not enable module-mode inside GOPATH https://github.com/golang/go/wiki/Modules#when-do-i-get-old-behavior-vs-new-module-based-behavior

@FRidh FRidh added this to Needs review in Staging Nov 19, 2019
@FRidh FRidh merged commit 490f8ab into NixOS:staging Dec 10, 2019
Staging automation moved this from Needs review to Done Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
8.has: documentation 10.rebuild-darwin: 501-1000 10.rebuild-darwin: 501+ 10.rebuild-linux: 501-1000 10.rebuild-linux: 501+
Projects
Staging
  
Done
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@marsam @jonringer @fpletz @FRidh