No description
Find a file
Peter Simons 64334a7b64 hackage-packages.nix: automatic Haskell package set update
This update was generated by hackage2nix v2.14.1-5-g0b4d758 from Hackage revision
c3f27250ec.
2019-02-18 10:39:12 +01:00
.github codeowners: fix reference to renamed file 2018-12-26 10:42:11 +01:00
doc Merge pull request #55138 from oxij/tree/random-fixes 2019-02-13 20:16:07 +00:00
lib Merge pull request #55129 from oxij/tree/move-defaults-to-package-files 2019-02-13 20:04:08 +00:00
maintainers Merge pull request #53563 from rbrewer123/feature/pyznap-init 2019-02-17 21:09:24 -08:00
nixos Merge pull request #55410 from aanderse/apache-defaults 2019-02-18 03:27:18 +01:00
pkgs hackage-packages.nix: automatic Haskell package set update 2019-02-18 10:39:12 +01:00
.editorconfig
.gitattributes
.gitignore Replace androidenv by new implementation 2018-12-18 21:16:06 +01:00
.version
COPYING COPYING: move notice to README.md 2018-10-13 13:22:18 +00:00
default.nix
README.md doc/reviewing-contributions: pull-requests -> pull requests 2018-11-19 13:03:23 -06:00

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.