Nix Packages collection & NixOS
Go to file
2018-12-02 10:34:54 +02:00
.github PULL_REQUEST_TEMPLATE: Ask for docs 2018-11-22 19:57:19 +01:00
doc Merge pull request #50977 from jtojnar/parallel-update.nix 2018-12-02 01:23:39 +01:00
lib Merge master into staging-next 2018-11-30 17:46:21 +01:00
maintainers ocamlPackages.opti: init at 1.0.3 2018-12-01 19:00:23 -08:00
nixos nixos/cockroachdb: create new service 2018-12-01 19:07:49 -06:00
pkgs Merge pull request #51372 from dtzWill/update/s-tui-0.8.3 2018-12-02 10:34:54 +02:00
.editorconfig Revert ".version: remove final newline" 2018-04-28 14:23:13 +02:00
.gitattributes gitattributes: disable merge=union in all-packages 2018-03-27 11:03:03 -05:00
.gitignore kde5: consolidate packages into desktops/kde-5 2016-03-01 10:36:00 -06:00
.version 18.09 -> 19.03 2018-09-02 16:45:00 -04:00
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.