Alyssa Ross
b33fd42c30
rustc 1.73.0 introduced a new x86_64-unikraft-linux-musl target. This triple is a bit of a lie — the kernel in this case is unikraft, which isn't Linux, it just tries to be compatible with it. But this User-Agent-like string of a triple now exists, and with it comes some fallout. Spidermonkey asks rustc for the list of supported targets, then picks the one that best matches the GNU triple it's building for, which in the native case config.guess will say is x86_64-pc-linux-musl. Prior to rustc 1.73.0, all was well, because there was only one x86_64 musl triple, but now there are two: x86_64-unknown-linux-musl, and x86_64-unikraft-linux-musl, and neither of those are obviously closer than the other to x86_64-pc-linux-musl to Spidermonkey's build system. As a result, it can't decide which target to pass to rustc, and bails out. We can fix this by telling Spidermonkey what platform it should be building for, rather than letting it guess, which previously we did only when cross compiling. This approach is already used in the Firefox derivation (which is why it was not affected by the rustc update), so it's been well tested already. Closes: https://github.com/NixOS/nixpkgs/pull/266560 Closes: https://github.com/NixOS/nixpkgs/pull/282923
Nixpkgs is a collection of over 80,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
- Community-maintained 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 23.11 release
- Tests for unstable/master
- Tests for the NixOS 23.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.