Nix Packages collection & NixOS
Go to file
Wael M. Nasreddine 28435e47b1
buildGoModule: function for packaging Go modules
The function buildGoModule builds Go programs managed with Go modules. It builds
a Go module through a two phase build:

- An intermediate fetcher derivation. This derivation will be used to
  fetch all of the dependencies of the Go module.
- A final derivation will use the output of the intermediate derivation
  to build the binaries and produce the final output.
2019-03-14 10:31:02 -07:00
.github .github/CODEOWNERS: remove @ryantm from haskell 2019-02-28 21:32:35 -08:00
doc buildGoModule: function for packaging Go modules 2019-03-14 10:31:02 -07:00
lib lib: add showWarnings 2019-03-08 11:19:18 +02:00
maintainers tamsyn: init at 1.11 2019-03-12 20:45:19 -07:00
nixos Merge pull request #57414 from primeos/sway-1.0 2019-03-13 22:40:37 +01:00
pkgs buildGoModule: function for packaging Go modules 2019-03-14 10:31:02 -07:00
.editorconfig
.gitattributes
.gitignore
.version 19.09 is Loris. 2019-02-25 23:21:14 +01:00
COPYING
default.nix
README.md

logo

Code Triagers Badge

Nixpkgs is a collection of packages for the Nix package manager. It is periodically built and tested by the Hydra build daemon as so-called channels. To get channel information via git, add nixpkgs-channels as a remote:

% git remote add channels https://github.com/NixOS/nixpkgs-channels.git

For stability and maximum binary package support, it is recommended to maintain custom changes on top of one of the channels, e.g. nixos-18.09 for the latest release and nixos-unstable for the latest successful build of master:

% git remote update channels
% git rebase channels/nixos-18.09

For pull requests, please rebase onto nixpkgs master.

NixOS Linux distribution source code is located inside nixos/ folder.

Communication:

Note: MIT license does not apply to the packages built by Nixpkgs, merely to the package descriptions (Nix expressions, build scripts, and so on). It also might not apply to patches included in Nixpkgs, which may be derivative works of the packages to which they apply. The aforementioned artifacts are all covered by the licenses of the respective packages.