3
0
Fork 0
forked from mirrors/nixpkgs
Nix Packages collection
Go to file
Nick Novitski 6e07691ed7 androidenv: remove android command from fetch.sh
It's deprecated, and no longer prints the urls of any xml files for the script
to parse.
2018-10-26 20:45:51 -07:00
.github CONTRIBUTING.md: Clarify clarification on periods 2018-10-10 21:06:12 +00:00
doc nixpkgs docs: Fix tiny typo (#48477) 2018-10-23 14:41:15 +00:00
lib Merge pull request #48680 from markuskowa/licenses-22 2018-10-18 23:40:02 +02:00
maintainers ocamlPackages.zmq: init at 20180726 2018-10-22 06:51:17 +00:00
nixos nixos/rootston: Remove the module and the package (#48905) 2018-10-23 20:38:33 +02:00
pkgs androidenv: remove android command from fetch.sh 2018-10-26 20:45:51 -07: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 COPYING: move notice to README.md 2018-10-13 13:22:18 +00: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.