New features core: add variable "old_full_name" in buffer, set during buffer renaming (issue weechat/weechat#1428) core: add debug option "-d" in command /eval (issue weechat/weechat#1434) api: add functions crypto_hash and crypto_hash_pbkdf2 api: add info "auto_connect" (issue weechat/weechat#1453) api: add info "weechat_headless" (issue weechat/weechat#1433) buflist: add pointer "window" in bar item evaluation irc: add support of fake servers (no I/O, for testing purposes) relay: accept hash of password in init command of weechat protocol with option "password_hash" (PBKDF2, SHA256, SHA512) relay: reject client with weechat protocol if password or totp is received in init command but not set in WeeChat (issue weechat/weechat#1435) Bug fixes core: fix memory leak in completion core: flush stdout/stderr before forking in hook_process function (issue weechat/weechat#1441) core: fix evaluation of condition with nested "if" (issue weechat/weechat#1434) irc: split AUTHENTICATE message in 400-byte chunks (issue weechat/weechat#1459) irc: copy temporary server flag in command /server copy irc: add nick changes in the hotlist (except self nick change) irc: case-insensitive comparison on incoming CTCP command, force upper case on CTCP replies (issue weechat/weechat#1439) irc: fix memory leak when the channel topic is changed logger: fix crash when logging is disabled on a buffer and the log file was deleted in the meanwhile, when option logger.file.info_lines is on (issue weechat/weechat#1444) php: fix crash when loading script with PHP 7.4 (issue weechat/weechat#1452) relay: update buffers synchronization when buffers are renamed (issue weechat/weechat#1428) script: fix memory leak in read of script repository file if it has invalid content script: fix unexpected display of scripts list in buffer with command /script list -i xfer: send signal "xfer_ended" after the received file has been renamed (issue weechat/weechat#1438) Tests scripts: fix generation of test scripts with Python 3.8 unit: add tests on IRC protocol functions and callbacks unit: add tests on function secure_derive_key unit: add tests on functions util_get_time_diff and util_file_get_content Build core: fix Cygwin build guile: add detection of Guile 3.0.0 (issue weechat/weechat#1442) irc: fix build with GnuTLS < 3.1.0 (issue weechat/weechat#1431) php: add detection of PHP 7.4 ruby: add detection of Ruby 2.7 (issue weechat/weechat#1455) |
||
---|---|---|
.github | ||
doc | ||
lib | ||
maintainers | ||
nixos | ||
pkgs | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.version | ||
COPYING | ||
default.nix | ||
flake.nix | ||
README.md |
Nixpkgs is a collection of over 40,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
- IRC - #nixos on freenode.net
- NixOS Weekly
- Community-maintained wiki
- Community-maintained list of ways to get in touch (Discord, Matrix, Telegram, other IRC channels, 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
- 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 19.09 release
- Tests for unstable/master
- Tests for the NixOS 19.09 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 over 40,000 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 gostaging
is branched from master, changes that have a big impact on Hydra builds go to this branchstaging-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 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.