Silly nixpkgs mirror, totally harmless :3
Find a file
Samuel Dionne-Riel c113c094cf sd-image: Pull less slack in the image by accounting for slack
The slack, seemingly, accounted for more than the minimum required for
slack plus the two partitions.

This change makes the gap a somewhat abstracted amount, but is not
configurable within the derivation.
2019-06-16 17:47:31 -04:00
.github CODEOWNERS: Change me from all NixOS modules to just new ones 2019-05-01 20:32:02 +02:00
doc doc: update nixpkgs-mozilla rev 2019-06-08 16:15:32 +02:00
lib Merge pull request #62712 from danbst/module-conflict-naming 2019-06-13 11:59:54 +03:00
maintainers Merge #63071: maintainers: add dmvianna 2019-06-13 10:13:22 +02:00
nixos sd-image: Pull less slack in the image by accounting for slack 2019-06-16 17:47:31 -04:00
pkgs iamy: 2.1.1 -> 2.3.2 (#62613) 2019-06-13 12:14:16 -07:00
.editorconfig
.gitattributes
.gitignore
.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
README.md README: 18.09 -> 19.03 2019-04-28 19:15:08 +02: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-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.