nordic-dev.net/nixpkgs
nordic-dev.net/nixpkgs
2
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2025-01-14 08:54:46 +00:00
Code Issues Packages Projects Releases Wiki Activity
Nix Packages collection & NixOS
709,127 Commits 172 Branches 125 Tags 7.4 GiB
Nix 95.3%
Shell 2%
Python 1.5%
Perl 0.2%
Rust 0.2%
Other 0.3%
2995b3825e
Go to file
Maximilian Bosch 2995b3825e
nixos/pgbouncer: rework RFC42 integration 
Commit bfb9d1825d added RFC42 support
which is a good thing in general, but this implementation has the
following flaws:

* `services.pgbouncer.logFile` was not renamed to `[...].log_file`, but
  to `[...].logfile`. Also the use of `mkRenamedOptionModule` is
  inappropriate here because the two options are not equivalent: the old
  option took a path relative to the home directory, the new an absolute
  path.

* Using `mkRenamedOptionModule` with options that don't exist (but are
  keys in a freeform attr-set or an `attrsOf X`), you get the following
  error when referencing an option you didn't declare:

    error: evaluation aborted with the following error message: 'Renaming error: option `services.pgbouncer.settings.pgbouncer.listen_port' does not exist.'

  This error is pretty bad because it's not actionable for an end-user of
  the module. A possible use-case is doing

    networking.firewall.allowedTCPPorts = [ config.services.pgbouncer.listenPort ];

  without specifying a custom listen port. This is an example of why you
  want to keep options, they already contain defaults and you can re-use
  those defaults in other parts of your system configuration.

  I decided to re-add a bunch of options where I figured that it's
  either useful to be able to address those in the NixOS configuration
  or having documentation directly in the options' reference in the
  NixOS manual.

  I didn't add all options, I'll leave that to the maintainers of
  pgbouncer.
2024-11-22 17:01:36 +01:00
.github nixos-rebuild-ng: init 2024-11-15 18:27:16 +00:00
ci nixos-rebuild-ng: init 2024-11-15 18:27:16 +00:00
doc rustPlatform.fetchCargoVendor: init (#349360) 2024-11-16 09:30:53 +05:30
lib lib/licenses: add missing spdxId and remove urls from licenses that have a spdxId (#340360) 2024-11-15 10:33:31 +01:00
maintainers maintainers: add felixzieger 2024-11-16 01:37:09 +01:00
nixos nixos/pgbouncer: rework RFC42 integration 2024-11-22 17:01:36 +01:00
pkgs writers: make babashka interpreter and check configurable (#354760) 2024-11-16 21:09:31 +01:00
.editorconfig
.git-blame-ignore-revs .git-blame-ignore-revs: add 'treewide: migrate packages to pkgs/by-name, take 1' 2024-11-09 20:41:28 +08:00
.gitattributes
.gitignore
.mailmap maintainers: update entry for kloenk 2024-11-04 12:02:07 +01:00
.version
CONTRIBUTING.md 25.05 is Warbler 2024-11-14 09:10:54 -08:00
COPYING
default.nix
flake.nix
README.md README: use relative links to CONTRIBUTING.md (#211584) 2024-11-12 11:37:49 +05:30
shell.nix

README.md

NixOS logo

Contributors badge Open Collective supporters

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

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.

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.