Nix Packages collection & NixOS
Go to file
Paul Tötterman 23a84e939e nixos/docker-registry: fix listenAddress
listenAddress config option was previously unused in config generation
2019-02-08 14:39:22 +02:00
.github codeowners: fix reference to renamed file 2018-12-26 10:42:11 +01:00
doc Fix typos in docker tools docs 2019-01-30 16:37:43 +00:00
lib types.optionSet: deprecate and remove last usages 2019-01-31 00:41:10 +02:00
maintainers Merge pull request #55203 from Shou/init-openapi-generator 2019-02-07 21:29:01 +01:00
nixos nixos/docker-registry: fix listenAddress 2019-02-08 14:39:22 +02:00
pkgs Merge pull request #55368 from jhillyerd/chezmoi 2019-02-08 12:51:16 +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 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.