Moritz Heidkamp
a49ee8d7de
Most eggs in the canonical repository don't declare a `version` property in their `.egg` files. This is because it's provided implicitly when using `chicken-install` to retrieve them. Quoting from [the manual](https://wiki.call-cc.org/man/5/Egg%20specification%20format#version): > Eggs from remote egg servers are automatically versioned - the version is part of the protocol to retrieve the egg and does not have to be specified in the .egg file. Since we don't use `chicken-install` to retrieve eggs, this leaves us with a version of "unknown" in most cases, e.g.: $ nix-shell -p chickenPackages.chickenEggs.json-abnf chickenPackages.chicken --run chicken-status abnf ...................................................... version: unknown iset ...................................................... version: unknown json-abnf ................................................. version: unknown lexgen .................................................... version: unknown regex ......................................................... version: 2.0 srfi-1 .................................................... version: unknown srfi-127 .................................................. version: unknown srfi-69 ................................................... version: unknown utf8 ...................................................... version: unknown This is usually not an issue unless another egg declares a minimum required version dependency on an egg with missing version info. In this case, `chicken-install` will fill in "0.0.0" as a fallback and the check will fail. This has so far been worked around patches (see e.g. #346004 or #358455). This patch addresses the root cause by following the documentation's recommendation: > Eggs installed from local directories (see below) should explicitly specify a version. To do that, `eggDerivation` now simply always adds the version to the generated `.egg-info` file. This has the added benefit of correcting potentially inconsistent version declarations in `.egg` files. Note that we cannot patch the original `.egg` file because not all released egg versions match [the stricter version format validation which currently applies there](https://bugs.call-cc.org/ticket/1855). The patch also changes the signature of `eggDerivation` to allow passing in `pname` and `version` instead of `name` to allow for easy access to the egg version. However, for backwards compatibility, the old `name` argument is also still supported. As a result, the aforementioned overrides are removed again and some additional eggs can be marked as unbroken again. And finally, this is the output of the above `chicken-status` call with the patch applied: $ nix-shell -p chickenPackages.chickenEggs.json-abnf chickenPackages.chicken --run chicken-status abnf .......................................................... version: 8.3 iset .......................................................... version: 2.2 json-abnf ..................................................... version: 7.0 lexgen ........................................................ version: 8.2 regex ......................................................... version: 2.0 srfi-1 ...................................................... version: 0.5.1 srfi-127 ...................................................... version: 1.3 srfi-69 ..................................................... version: 0.4.3 utf8 ........................................................ version: 3.6.3
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 25.05 release
- Tests for unstable/master
- Tests for the NixOS 25.05 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.