49be064fa5
Hello, New versions of all the skarnet.org packages are available. This is mostly a bugfix release (there was an installation bug in some circumstances with shared libraries) but some packages, notably execline and s6, have new, useful features. The new versions are the following: skalibs-2.9.2.0 nsss-0.0.2.2 utmps-0.0.3.2 execline-2.6.0.0 s6-2.9.1.0 s6-rc-0.5.1.2 s6-linux-init-1.0.4.0 s6-dns-2.3.2.0 s6-networking-2.3.1.2 s6-portable-utils-2.2.2.2 s6-linux-utils-2.5.1.2 mdevd-0.1.1.2 bcnm-0.0.1.0 Here are details for the packages that have more than bugfixes: * skalibs-2.9.2.0 --------------- - New header: skalibs/bigkv.h. It's a set of functions allowing efficient lookups in a large set of strings (typically read from the command line or the environment). https://skarnet.org/software/skalibs/ git://git.skarnet.org/skalibs * execline-2.6.0.0 ---------------- - It's a major release because an API has been modified: dollarat. Beforehand, dollarat's -0 option would always prevail over any -d option. Now, dollarat has its conflicting -0 and -d options handled in the conventional way, with rightmost priority. - The runblock program now accepts a command line prefix, which is given as runblock's own command line. This allows blocks to serve as arguments to a new command, instead of having to be full command lines by themselves. - New binary: posix-umask. - The former "cd" program is now named "execline-cd" and the former "umask" program is named "execline-umask". When the=20 --enable-pedantic-posix option is not given at configure time, "cd" and "umask" are symbolic links created at installation time and pointing to execline-cd and execline-umask respectively. When the --enable-pedantic-posix option is given, the symbolic links point to posix-cd and posix-umask instead. - With posix-cd and posix-umask (and the changes to wait done in the previous version), execline is now fully POSIX-compliant when built with the --enable-pedantic-posix option. This will certainly, without the slightest hint of a doubt, change distributions' attitudes about it. https://skarnet.org/software/execline/ git://git.skarnet.org/execline * s6-2.9.1.0 ---------- - A new '?' directive has been added to s6-log. It behaves exactly like '!', except that it spawns the given processor with /bin/sh as an interpreter instead of execlineb. - execline support is now optional: it can be disabled by specifying --disable-execline at configure time. Some functionality is unavailable when execline support is disabled: * s6-log's '!' directive * s6-notifyoncheck's -c option * s6-ipcserver-access's support for 'exec' directives in a ruleset - A new -X option has been added to s6-svscan, to specify a descriptor that will be passed as stderr to a service spawned by this s6-svscan and named s6-svscan-log. This is used in the new s6-linux-init, to avoid needing to hardcode the /dev/console name for the catch-all logger's standard error. - On systems that define SIGPWR and SIGWINCH, s6-svscan -s now diverts those signals. This allows powerfail and kbrequest events to be handled when s6-svscan runs as process 1. https://skarnet.org/software/s6/ git://git.skarnet.org/s6 * s6-linux-init-1.0.4.0 --------------------- - New options have been added to s6-linux-init-maker: to support running s6-linux-init without a catch-all logger, and to support running it in a container. - s6-linux-init-maker now adds a SIGPWR handler to the default image: on receipt of a SIGPWR, the system's shutdown procedure is triggered. - s6-linux-init now handles kbrequest, which triggers a SIGWINCH in init when a special, configurable set of keys is pressed. By default, no SIGWINCH handler is declared in the image, and no set of keys is bound to kbrequest. https://skarnet.org/software/s6-linux-init/ git://git.skarnet.org/s6-linux-init * s6-dns-2.3.2.0 -------------- - New library: libdcache, implementing a clean cache structure to contain DNS data. It's still not used at the moment. https://skarnet.org/software/s6-dns/ git://git.skarnet.org/s6-dns * bcnm-0.0.1.0 ------------ - First numbered release, because the Ad=C3=A9lie Linux distribution, which uses libwpactrl, needs an official release instead of pulling from git. - libwpactrl is a set of C functions helping control a wpa_supplicant process. - bcnm-waitif is a binary that waits for network interface state events such as appearance/disappearance, up/down, running/not-running. It is useful to avoid race conditions during a boot sequence, for instance. https://skarnet.org/software/bcnm/ git://git.skarnet.org/bcnm Enjoy, Bug-reports welcome. -- Laurent |
||
|---|---|---|
| .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:
masteris the main branch where all small contributions gostagingis branched from master, changes that have a big impact on Hydra builds go to this branchstaging-nextis 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.