No description
Find a file
Michael Weiss 5d1abc68e7
signal-desktop: Document the build "expiration"
This adds a comment why it's important to always backport any updates as
suggested in #68232. I've als included a few more details to document
the behaviour.

Sources:
- Default build lifetime [0]
- asar - Electron Archive [1]

[0]: d3d2b0ec52/Gruntfile.js (L222)
[1]: https://github.com/electron/asar
2019-09-07 17:37:05 +02:00
.github CODEOWNERS: Add myself as owner for emacs 2019-08-30 17:23:13 +01:00
doc Merge branch 'master' into staging-next 2019-09-06 03:20:09 +02:00
lib Merge master into staging-next 2019-09-06 22:46:05 +02:00
maintainers lua*Packages.lua-yajl: init at 2.0-1 2019-09-07 23:05:55 +09:00
nixos nixos/kibana: Filter empty lists 2019-09-07 13:24:24 +01:00
pkgs signal-desktop: Document the build "expiration" 2019-09-07 17:37:05 +02:00
.editorconfig
.gitattributes
.gitignore
.version
COPYING COPYING: include 2019 2019-03-18 19:55:33 -07:00
default.nix
README.md README: add open collective badge 2019-07-17 14:27:28 +02:00

logo

Code Triagers Badge Open Collective supporters

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.

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.