Silly nixpkgs mirror, totally harmless :3
Find a file
Michael Raskin 545cbf1bc3
Merge pull request #54632 from fare-patches/master
Update gambit and gerbil from upstream
2019-01-28 10:33:29 +00:00
.github codeowners: fix reference to renamed file 2018-12-26 10:42:11 +01:00
doc nixpkgs/manual: add one more fix for a missed review 2019-01-27 12:01:23 -05:00
lib linux: convert hardened-config to a structured one 2019-01-28 09:07:24 +09:00
maintainers Merge pull request #54619 from Mic92/remove-wkennington 2019-01-26 23:37:27 +00:00
nixos Merge pull request #42838 from teto/kernel_autoconf 2019-01-28 10:38:00 +01:00
pkgs Merge pull request #54632 from fare-patches/master 2019-01-28 10:33:29 +00: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 Fix local path to release notes in error message 2018-10-08 05:43:15 -05:00
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.