Silly nixpkgs mirror, totally harmless :3
Find a file
Maximilian Bosch 4929ee7421
activator: remove attribute name
Back in 2017 I removed the `activator` package (see 25a3563102)
as it reached its end of life. Almost 2 years later everyone
shouldn't reference to this (not evaluating) path anymore
and hence can be removed.
2019-03-16 02:05:24 +01:00
.github .github/CODEOWNERS: remove @ryantm from haskell 2019-02-28 21:32:35 -08:00
doc Add word debug(ging) to breakpointHook description for discoverability 2019-03-15 19:33:21 +01:00
lib lib: add showWarnings 2019-03-08 11:19:18 +02:00
maintainers maintainers: add terlar 2019-03-15 22:26:04 +01:00
nixos Revert "nixos/nginx: support h2c" 2019-03-15 14:31:11 +01:00
pkgs activator: remove attribute name 2019-03-16 02:05:24 +01: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
default.nix
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.