Go to file

Robert Hensing afc60d017b nixos/qemu-vm: Use disposable EROFS for store when writableStore = false This avoids putting a large disk image in the store (and possibly in a binary cache), while improving runtime performance. Assuming you're running an SSD, and/or with plenty of cache (?) it is feasible to preempt the virtualization overhead before VM start, in single-digit seconds. For some tests that perform many reads on the store, the improved performance of EROFS is sufficient that not only the image creation overhead is compensated for, but is actually faster. Stats for nixosTests.gitlab: Baseline without useNixStoreImage: >1000s Baseline with useNixStoreImage without writableStore = false ext4 image in store: 277 seconds + significant image build time and/or disk space Disposable erofs image: 249 seconds _including_ image build time Custom erofs overlay on 9p host store: 391 seconds; presumably because the overlay still performs too many 9p accesses, or perhaps some other overhead. This solution had no obvious performance advantage, while requiring extra options to work, so it was discarded.		2022-07-17 14:56:35 +02:00
.github	terraform-providers: update 2022-07-10	2022-07-10 16:20:44 +10:00
doc	vimUtils: remove vam support	2022-07-10 20:38:09 +02:00
lib	lib/trivial: Update oldestSupportedRelease	2022-07-04 20:07:44 +02:00
maintainers	teams: add revol-xut to c3d2	2022-07-11 11:32:31 +02:00
nixos	nixos/qemu-vm: Use disposable EROFS for store when writableStore = false	2022-07-17 14:56:35 +02:00
pkgs	Merge pull request #181038 from r-ryantm/auto-update/cdk-go	2022-07-12 13:17:32 +02: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

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.

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.