Nix Packages collection & NixOS
Go to file
Chris Ostrouchov 19d077a157 pythonPackages.pygmo: 2.8 -> 2.9 refactor fix broken package
Introduce a `pagmo2WithPython` which overrides the pagmo2 expression
and enables the pygmo build. Then hand it over to `buildPythonPackage`
by making it the src to produce a usable package.
2018-12-18 10:11:49 -05:00
.github PULL_REQUEST_TEMPLATE: Ask for docs 2018-11-22 19:57:19 +01:00
doc doc/breakpointHook: correct typos 2018-12-13 21:36:29 +00:00
lib Merge pull request #51884 from alyssais/bundlerEnv-groups 2018-12-12 23:51:52 +00:00
maintainers Merge pull request #51018 from plchldr/rtl8821a 2018-12-17 23:36:36 -06:00
nixos Merge pull request #52458 from tadfisher/emacs-bash-prompt 2018-12-18 09:19:48 +00:00
pkgs pythonPackages.pygmo: 2.8 -> 2.9 refactor fix broken package 2018-12-18 10:11:49 -05:00
.editorconfig
.gitattributes
.gitignore
.version
COPYING COPYING: move notice to README.md 2018-10-13 13:22:18 +00:00
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.