Bernardo Meurer Costa
9fd2b8c767
Cargo sets `CARGO_BIN_EXE_<name>` when compiling integration tests so they can locate the crate's own binaries via `env!()` and exec them as subprocesses. buildRustCrate previously compiled bin targets as test harnesses only (via `--test`) when buildTests=true, so the real binary never existed and the env var was never set. When buildTests is set, now first build the real (non-test) binaries to `target/cargo-bin-exe/`, install them to `$out/bin/`, and expose `CARGO_BIN_EXE_<name>` to subsequent rustc invocations via an `env` prefix. Using `env` rather than bash `export` is necessary because hyphenated binary names (`CARGO_BIN_EXE_my-crate`) produce env var names that bash rejects as invalid identifiers; `env` sets them via execve's envp array directly and has no such restriction. The env array is populated by iterating `target/cargo-bin-exe/` at build time, so it covers all binary-target shapes: explicit `crateBin` entries, auto-detected `src/main.rs`, and auto-detected `src/bin/*.rs`. `build_bin` in lib.sh gains an optional third argument for the output directory so the real binary and the `--test` harness can coexist without colliding in `target/bin/`. The lib-test build is reordered to after the real-bin build so its compilation also sees the env vars.
Nixpkgs is a collection of over 120,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
- Discourse Forum
- Matrix Chat
- Official wiki
- Community-maintained list of ways to get in touch (Discord, Telegram, IRC, etc.)
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 Branding - NixOS branding
Continuous Integration and Distribution
Nixpkgs and NixOS are built and tested by our continuous integration system, Hydra.
- Continuous package builds for unstable/master
- Continuous package builds for the NixOS 25.11 release
- Tests for unstable/master
- Tests for the NixOS 25.11 release
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 like a lot at first, it helps to 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.