Silly nixpkgs mirror, totally harmless :3
Find a file
R. RyanTM fc5d1f48b4 cppcheck: 1.85 -> 1.86
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/cppcheck/versions
2018-12-16 01:59:44 -08:00
.github PULL_REQUEST_TEMPLATE: Ask for docs 2018-11-22 19:57:19 +01:00
doc docs: Remove nix-repl references 2018-12-03 21:37:54 -05:00
lib systems/parse.nix: support eabihf 2018-12-02 19:49:36 -06:00
maintainers buildPython*: add updateScript to passthru 2018-12-07 15:48:54 +01:00
nixos Merge master into staging-next 2018-12-08 12:40:13 +01:00
pkgs cppcheck: 1.85 -> 1.86 2018-12-16 01:59:44 -08:00
.editorconfig
.gitattributes
.gitignore
.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.