Liam Murphy
d4a8babe90
It was already reproducible: the only reason it seemed not to be was due
to a quirk of how `--rebuild` works on macOS. Since the implementation
of the Nix sandbox on macOS is unable to change the meaning of paths,
when rebuilding a derivation, it can't be done at the same path as the
original. Instead, the rebuild occurs with a different output path, and
the output is scanned for instances of that path so that they can be
replaced with the correct one afterwards (ala ca-derivations).
Unfortunately, macOS's codesigning system seems to include the hash of
the signed binary as part of its signature, including any incorrect
paths it contains. This results in the binaries still being different
after the path replacement step has occured.
The reason to go out of our way to revert this is that the workaround to
avoid including the output path in any binaries includes replacing the
install name of judy with `@rpath/*` rather than its absolute path,
which breaks at least one dependency that doesn't add it to RPATH
(gtkwave), and possibly others.
To confirm that it's reproducible:
```
drv=$(nix eval .#judy --apply "pkg: (pkg.overrideAttrs { __REBUILD = true; }).drvPath" --raw)
out=$(nix derivation show "$drv" | jq -r ".[].outputs.out.path")
nix build "$drv^*" --no-link
cp -r "$out" rebuild-1
nix store delete "$out" --option keep-outputs false
nix build "$drv^*" --no-link
cp -r "$out" rebuild-2
diff -r rebuild-1 rebuild-2
```
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
- 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.