03d6c406fc
It is referenced in various places, but does not work out of the box: $ nixos-help /run/current-system/sw/bin/nixos-help: unable to start a web browser; please set $BROWSER In the user-hidden fallbacks to xdg-open(1) and w3m(1), `nixos-help` expects tools to be deliberately installed by users. For default installations and new users in general, this is unlikely to be the case. Conversely, chances to use `nixos-help` are even higher in such cases. Use w3m-nographics by default to ensure documentation is always available. The documentation browser on ttyS8 already does so, but is not accessible in every installation, e.g. VMs with only ttyS0 and SSH available. This obsoletes including it in the base profile's systemPackages, so remove the @TODO as done.
Nixpkgs is a collection of packages for the Nix package manager. It is periodically built and tested by the Hydra build daemon as so-called channels. To get channel information via git, add nixpkgs-channels as a remote:
% git remote add channels https://github.com/NixOS/nixpkgs-channels.git
For stability and maximum binary package support, it is recommended to maintain
custom changes on top of one of the channels, e.g. nixos-19.03 for the latest
release and nixos-unstable for the latest successful build of master:
% git remote update channels
% git rebase channels/nixos-19.03
For pull requests, please rebase onto nixpkgs master.
NixOS Linux distribution source code is located inside
nixos/ folder.
- NixOS installation instructions
- Documentation (Nix Expression Language chapter)
- Manual (How to write packages for Nix)
- Manual (NixOS)
- Community maintained wiki
- Continuous package builds for unstable/master
- Continuous package builds for 19.03 release
- Tests for unstable/master
- Tests for 19.03 release
Communication:
Note: MIT license does not apply to the packages built by Nixpkgs, merely to the package descriptions (Nix expressions, build scripts, and so on). 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.