| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | buildGoPackage: disable module-mode | Mario Rodas | 2019-12-10 |
| | | | | | | | | | | | | | | 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 | ||
| * | buildGoPackage: enable cross compilation | Ding Xiang Fei | 2019-06-25 |
| | | |||
| * | buildGoPackage: keep string context (#63680) | Matthew Bauer | 2019-06-22 |
| | | | | | | | | | | | | In Nix, each string has a context that it carries of where it originated. Some functions like filterAttrs modify the context of its args when doing comparisons. That is important because we use the string context of “name” to get where a derivation was defined. This causes some builtins like unsafeGetAttrPos to report incorrectly that the string was set in lib/attrsets.nix and reporting that as the source file. Using removeAttrs avoids this problem. Fixes #63679 | ||
| * | buildGoPackage: move it under a different path | Wael M. Nasreddine | 2019-03-13 |
| This change moves buildGoPackage from pkgs/development/go-modules to pkgs/development/go-packages, so we can have buildGoModule at pkgs/development/go-modules. | |||