No description
Find a file
Timo Kaufmann 0cfd90a109 buildBazelPackage: fix directory symlink handling
The previous behaviour would work fine as long as `symlink` is a link to
a file. If is a link to a directory though, the new `ln` wouldn't
overwrite it but would create a new link *in that directory* (with the
name of the link source).

Instead, we can precompute the target location, then first remove the
symlink and write the new one in its place.
2019-06-20 18:35:16 +02:00
.github CODEOWNERS: Change me from all NixOS modules to just new ones 2019-05-01 20:32:02 +02:00
doc doc/idris: Fix install instructions (#63163) 2019-06-19 17:10:21 +02:00
lib treewide: remove unused variables (#63177) 2019-06-16 19:59:05 +00:00
maintainers maintainers: add magenbluten 2019-06-19 15:01:27 +02:00
nixos Merge pull request #63204 from michaelpj/imp/localtime-upstream 2019-06-19 08:38:03 -04:00
pkgs buildBazelPackage: fix directory symlink handling 2019-06-20 18:35:16 +02:00
.editorconfig
.gitattributes
.gitignore
.version 19.09 is Loris. 2019-02-25 23:21:14 +01:00
COPYING COPYING: include 2019 2019-03-18 19:55:33 -07:00
default.nix
README.md README: 18.09 -> 19.03 2019-04-28 19:15:08 +02:00

logo

Code Triagers Badge

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.