No description
Find a file
Matthieu Coudron 7ec21fa162 vimPlugins.coc-nvim: init at v0.0.67
you still need to enable the node js provider in your nvim config
yarn is optional.
Run :checkhealth within neovim if you have any doubt.
2019-05-21 22:47:34 +09:00
.github CODEOWNERS: Change me from all NixOS modules to just new ones 2019-05-01 20:32:02 +02:00
doc Update haskell.section.md (#61685) 2019-05-18 16:01:49 -05:00
lib Merge pull request #60406 from JohnAZoidberg/remove-isnull 2019-05-18 09:36:24 +00:00
maintainers Merge pull request #61748 from dotlambda/pysonos 2019-05-20 13:22:58 +02:00
nixos nixos/nextcloud: Add options services.nextcloud.autoUpdateApps 2019-05-21 13:24:23 +02:00
pkgs vimPlugins.coc-nvim: init at v0.0.67 2019-05-21 22:47:34 +09: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
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.