No description
Find a file
R. RyanTM 429724a75b stress-ng: 0.09.59.1 -> 0.10.00
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/stress-ng/versions
2019-07-20 12:59:52 -07:00
.github Update FUNDING.yml 2019-07-17 14:22:24 +02:00
doc Merge master into staging-next 2019-07-13 09:45:40 +02:00
lib make-tarball / lib-tests: reduce duplication 2019-07-11 18:02:05 +02:00
maintainers Change maintainter's name 2019-07-19 09:21:18 +02:00
nixos nixos/doc: fix build 2019-07-18 20:40:24 -04:00
pkgs stress-ng: 0.09.59.1 -> 0.10.00 2019-07-20 12:59:52 -07:00
.editorconfig
.gitattributes
.gitignore Replace androidenv by new implementation 2018-12-18 21:16:06 +01:00
.version 19.09 is Loris. 2019-02-25 23:21:14 +01:00
COPYING COPYING: include 2019 2019-03-18 19:55:33 -07:00
default.nix Fix local path to release notes in error message 2018-10-08 05:43:15 -05:00
README.md README: add open collective badge 2019-07-17 14:27:28 +02:00

logo

Code Triagers Badge Open Collective supporters

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-19.03 for the latest release and nixos-unstable for the latest successful build of master:

% git remote update channels
% git rebase channels/nixos-19.03

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.