1
0
Fork 1
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-11-19 04:02:10 +00:00
Nix Packages collection
Go to file
Alyssa Ross 20ed441141 sonic-pi: don't use EOL Ruby
This was added to fix a compiler error in
4bc516aa54, where it was noted that it
still segfaulted after boot. Since it compiles with our default Ruby
now, I have to assume that the problem the override was added to set
has since been resolved. I don't know how to actually test, however.
2019-09-07 13:09:17 +00:00
.github CODEOWNERS: Add myself as owner for emacs 2019-08-30 17:23:13 +01:00
doc Merge branch 'master' into staging-next 2019-09-06 03:20:09 +02:00
lib Merge master into staging-next 2019-09-06 22:46:05 +02:00
maintainers Merge branch 'master' into staging-next 2019-09-04 11:00:56 +02:00
nixos nixos/kibana: Filter empty lists 2019-09-07 13:24:24 +01:00
pkgs sonic-pi: don't use EOL Ruby 2019-09-07 13:09:17 +00:00
.editorconfig
.gitattributes
.gitignore
.version
COPYING
default.nix
README.md README: add open collective badge 2019-07-17 14:27:28 +02:00

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.