b12f/nixpkgs
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
393314 commits 2 branches 0 tags 3.3 GiB
Nix 95.6%
Shell 1.9%
Python 1.2%
Perl 0.3%
C 0.3%
Other 0.3%
Find a file
Alyssa Ross c01c68bf1c crosvm.updateScript: stop trying manifest-versions 
manifest-versions never seems to contain the release build any more,
so we can't use it to find the version of crosvm being served to CrOS
devices.

Instead, I've changed the update script to take the latest version of
the appropriate crosvm Chrome OS release branch.  This is the branch
that gets served.  Every release, it is branched off from the
"chromeos" branch (which is the one that passes Chrome OS QA), and
then collects any critical fixes over the lifetime of the release.

With this change, I've introduced a new, simplified versioning
scheme, e.g. 100.0.  The tip build is always 1:1 with the Chrome
version, so having both of those is redundant.  The other number is
the number of commits that have been added to the release branch after
branching from the chromeos branch, so that the number will go up if
we update to include a new commit from the same release.
2022-07-21 16:30:56 +00:00
.github Merge pull request #180228 from fricklerhandwerk/codeowners-doc 2022-07-13 11:23:02 +02:00
doc Merge pull request #177219 from kenranunderscore/correct-nixpkgs-review-invocations-in-docs 2022-07-21 14:40:39 +02:00
lib Merge pull request #160554 from Cloudef/android-prebuilt 2022-07-18 10:01:00 +02:00
maintainers maintainers: papojari → annaaurora 2022-07-20 01:47:30 +02:00
nixos Merge pull request #181674 from nrdxp/nvidia-udev 2022-07-21 09:00:47 -07:00
pkgs crosvm.updateScript: stop trying manifest-versions 2022-07-21 16:30:56 +00:00
.editorconfig .editorconfig: allow trailing whitespace for markdown manual files 2022-04-21 09:00:11 +02:00
.git-blame-ignore-revs git-blame-ignore-revs: add python format commit 2022-06-06 09:00:59 +02:00
.gitattributes
.gitignore .gitignore: prepend slash to result and source 2022-06-10 08:17:12 -03:00
.version 22.11 is Raccoon 2022-05-23 20:08:07 +02:00
CONTRIBUTING.md CONTRIBUTING.md: use 22.05 as target branch for backports 2022-05-31 10:07:21 +02:00
COPYING
default.nix
flake.nix lib.systems: remove supported, replace with flakeExposed 2022-05-23 15:27:30 +02:00
README.md README: 21.11 -> 22.05 2022-05-31 08:36:12 +02:00

README.md

NixOS logo NixOS logo

Contributors badge Open Collective supporters

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

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.

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. When pull requests are made, our tooling automation bot, OfBorg will perform various checks to help ensure expression quality.

The Nixpkgs maintainers are people who have assigned themselves to maintain specific individual packages. We encourage people who care about a package to assign themselves as a maintainer. When a pull request is made against a package, OfBorg will notify the appropriate maintainer(s). The Nixpkgs committers are people who have been given permission to merge.

Most contributions are based on and merged into these branches:

  • master is the main branch where all small contributions go
  • staging is branched from master, changes that have a big impact on Hydra builds go to this branch
  • staging-next is branched from staging and only fixes to stabilize and security fixes with a big impact on Hydra builds should be contributed to this branch. This branch is merged into master when deemed of sufficiently high quality

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.