Peter CollingbourneandBjørn Forsman
bfefc8d2f3
After #400734 the path to the binutils wrapper is no longer passed via -B and is instead passed via $PATH. This had the following consequences for gnat-bootstrap: - GCC appends $prefix/$triple/bin to collect2's $COMPILER_PATH, which is where gnat-bootstrap's bundled linker binary is installed. For normal gcc packages, this has no impact on linker selection because binutils and gcc are installed to separate prefixes. - -B paths are also added to $COMPILER_PATH but they appear before $prefix/$triple/bin. This meant that gnat-bootstrap's collect2 would find the binutils wrapper before #400734. - collect2 searches for the linker on $PATH but only after failing to find it on $COMPILER_PATH. Because #400734 caused the binutils wrapper path to be removed from $COMPILER_PATH while the bundled linker on $prefix/$triple/bin was still present, gnat-bootstrap started finding the bundled linker on $COMPILER_PATH after #400734. The bundled ld binaries should not be used by builds utilizing gnat-bootstrap because we need our binutils wrappers to be used so that RPATH is set correctly. The ld binaries are unused as far as I'm aware, so remove them from the package so that collect2 finds the binutils wrapper on $PATH.
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
- NixOS Weekly
- 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 Artwork - NixOS artwork
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 24.11 release
- Tests for unstable/master
- Tests for the NixOS 24.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 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.