You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Andreas Rammhold 862615b86e
nixos/release: make ipv6 tests as important as legacy IP tests
4 years ago
.github .github/CODEOWNERS: remove @ryantm from haskell 4 years ago
doc Add word `debug(ging)` to breakpointHook description for discoverability 4 years ago
lib Doc fix: use correct function name in type signature for concatIMapStringsSep 4 years ago
maintainers kanshi: init at 2019-02-02 4 years ago
nixos nixos/release: make ipv6 tests as important as legacy IP tests 4 years ago
pkgs Merge pull request #56689 from andir/firefox66 4 years ago
.editorconfig Modified .editorconfig to apply indentation style to docbook files 5 years ago
.gitattributes gitattributes: disable merge=union in all-packages 5 years ago
.gitignore Replace androidenv by new implementation 4 years ago
.version 19.09 is Loris. 4 years ago
COPYING COPYING: move notice to 4 years ago doc/reviewing-contributions: pull-requests -> pull requests 4 years ago
default.nix Fix local path to release notes in error message 4 years ago


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

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.


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.