My personal project and infrastructure archive
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
xrelkd 3cb3d7f5f4 tilt: 0.8.8 -> 0.9.2 5 years ago
.github github: use the new issue template (#64983) 5 years ago
doc doc: put Java software's build-time dependencies into nativeBuildInputs 5 years ago
lib make-tarball / lib-tests: reduce duplication 5 years ago
maintainers Merge pull request #61701 from livnev/tree-from-tags 5 years ago
nixos thelounge: init at 3.0.1 (#51947) 5 years ago
pkgs tilt: 0.8.8 -> 0.9.2 5 years ago
.editorconfig Revert ".version: remove final newline" 6 years ago
.gitattributes gitattributes: disable merge=union in all-packages 6 years ago
.gitignore Replace androidenv by new implementation 6 years ago
.version 19.09 is Loris. 5 years ago
COPYING COPYING: include 2019 5 years ago
README.md README: add open collective badge 5 years ago
default.nix Fix local path to release notes in error message 6 years ago

README.md

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.