Nix Packages collection & NixOS
Go to file
2024-08-18 14:21:41 +08:00
.github CODEOWNERS: fix forgejo path after refactor 2024-08-17 21:11:53 +02:00
ci ci/pinned-nixpkgs.json: update 2024-07-18 15:52:11 +02:00
doc Merge pull request #333236 from nbraud/testers/runCommand 2024-08-16 18:07:41 -07:00
lib Merge pull request #329964 from Artturin/androidrenamesdk 2024-08-17 19:22:42 +03:00
maintainers Merge pull request #330745 from jhollowe-forks/hamrs 2024-08-18 00:16:20 -05:00
nixos Merge pull request #335366 from adamcstephens/incus/publish-squashfs 2024-08-17 19:06:02 -04:00
pkgs Merge pull request #335333 from wineee/qtcreator-14.0.1 2024-08-18 14:21:41 +08:00
.editorconfig .editorconfig: accept package.json indent as is 2024-07-29 19:24:33 +02:00
.git-blame-ignore-revs darwin.stdenv: update .git-blame-ignore-revs 2024-08-11 23:11:26 -04:00
.gitattributes
.gitignore Ignore Direnv files 2024-07-23 17:06:34 +07:00
.mailmap maintainers: update Atemu's emails 2024-08-06 03:22:34 +02:00
.version .version: Make lib/.version source of truth 2024-02-26 22:34:10 +01:00
CONTRIBUTING.md CONTRIBUTING.md: Mention nixfmt instead of manual formatting rules 2024-07-26 00:37:42 +02:00
COPYING COPYING: 2023 -> 2024 2024-01-30 16:49:51 +01:00
default.nix
flake.nix flake.nix: add pinned devshell 2024-08-09 19:25:59 -07:00
README.md Release NixOS 24.05 2024-05-31 20:17:44 +02:00
shell.nix root: add nixpkgs-review to shell.nix 2024-07-13 16:04:07 +02:00

NixOS logo

Contributors badge Open Collective supporters

Nixpkgs is a collection of over 100,000 software packages that can be installed with the Nix package manager. It also implements NixOS, a purely-functional Linux distribution.

Manuals

  • NixOS Manual - how to install, configure, and maintain a purely-functional Linux distribution
  • Nixpkgs Manual - contributing to Nixpkgs and using programming-language-specific Nix expressions
  • Nix Package Manager Manual - how to write Nix expressions (programs), and how to use Nix command line tools

Community

Other Project Repositories

The sources of all official Nix-related projects are in the NixOS organization on GitHub. Here are some of the main ones:

  • Nix - the purely functional package manager
  • NixOps - the tool to remotely deploy NixOS machines
  • nixos-hardware - NixOS profiles to optimize settings for different hardware
  • Nix RFCs - the formal process for making substantial changes to the community
  • NixOS homepage - the NixOS.org website
  • hydra - our continuous integration system
  • NixOS Artwork - NixOS artwork

Continuous Integration and Distribution

Nixpkgs and NixOS are built and tested by our continuous integration system, Hydra.

Artifacts successfully built with Hydra are published to cache at https://cache.nixos.org/. When successful build and test criteria are met, the Nixpkgs expressions are distributed via Nix channels.

Contributing

Nixpkgs is among the most active projects on GitHub. While thousands of open issues and pull requests might seem a lot at first, it helps consider it in the context of the scope of the project. Nixpkgs describes how to build tens of thousands of pieces of software and implements a Linux distribution. The GitHub Insights page gives a sense of the project activity.

Community contributions are always welcome through GitHub Issues and Pull Requests.

For more information about contributing to the project, please visit the contributing page.

Donations

The infrastructure for NixOS and related projects is maintained by a nonprofit organization, the NixOS Foundation. To ensure the continuity and expansion of the NixOS infrastructure, we are looking for donations to our organization.

You can donate to the NixOS foundation through SEPA bank transfers or by using Open Collective:

License

Nixpkgs is licensed under the MIT License.

Note: MIT license does not apply to the packages built by Nixpkgs, merely to the files in this repository (the Nix expressions, build scripts, NixOS modules, etc.). 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.